Vulnerability-Lookup

GHSA-HGH8-4RM3-F2VP

Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31

Details

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION

smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags. Those four bytes go to the client as they are found in the response buffer.

The buffer is zeroed on allocation, so a standalone request leaks nothing. A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.

ksmbd does not implement quota tracking, so report no control flags.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-99114"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-28T11:17:30Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION\n\nsmb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION,\nthat is the whole of struct smb2_fs_control_info, but never assigns\nFileSystemControlFlags.  Those four bytes go to the client as they are\nfound in the response buffer.\n\nThe buffer is zeroed on allocation, so a standalone request leaks\nnothing.  A compound request can leak: the offset of the next response\nis advanced by the length pinned for the previous one, so a reply that\nwas written into the buffer and then dropped in favour of the short\nerror response of smb2_set_err_rsp() stays there, and the next reply is\nlaid over it with only the header cleared.\n\nksmbd does not implement quota tracking, so report no control flags.",
  "id": "GHSA-hgh8-4rm3-f2vp",
  "modified": "2026-10-28T12:31:03Z",
  "published": "2026-10-28T12:31:03Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99114"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/03bb4338c3a7c3fc4decf699a35753f0891aab2a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d8c450ad0d08980b39b08d435efa921086c8b227"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-99114 (GCVE-0-2026-99114)

Vulnerability from cvelistv5 – Published: 2026-10-28 10:34 – Updated: 2026-10-28 10:34

Title

ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION

Summary

In the Linux kernel, the following vulnerability has been resolved: ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags. Those four bytes go to the client as they are found in the response buffer. The buffer is zeroed on allocation, so a standalone request leaks nothing. A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared. ksmbd does not implement quota tracking, so report no control flags.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 7033 records in the last 180 days details

References

3 references

URL	Tags
https://git.kernel.org/stable/c/d8c450ad0d08980b3…
https://git.kernel.org/stable/c/03bb4338c3a7c3fc4…
https://git.kernel.org/stable/c/c0cd3fc6824122014…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 , < d8c450ad0d08980b39b08d435efa921086c8b227 (git) Affected: e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 , < 03bb4338c3a7c3fc4decf699a35753f0891aab2a (git) Affected: e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 , < c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e (git)
Linux	Linux	Affected: 5.15 Unaffected: 0 , < 5.15 (semver) Unaffected: 6.18.59 , ≤ 6.18.* (semver) Unaffected: 7.2.13 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/smb/server/smb2pdu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d8c450ad0d08980b39b08d435efa921086c8b227",
              "status": "affected",
              "version": "e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9",
              "versionType": "git"
            },
            {
              "lessThan": "03bb4338c3a7c3fc4decf699a35753f0891aab2a",
              "status": "affected",
              "version": "e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9",
              "versionType": "git"
            },
            {
              "lessThan": "c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e",
              "status": "affected",
              "version": "e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/smb/server/smb2pdu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.15"
            },
            {
              "lessThan": "5.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.59",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.59",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.13",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION\n\nsmb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION,\nthat is the whole of struct smb2_fs_control_info, but never assigns\nFileSystemControlFlags.  Those four bytes go to the client as they are\nfound in the response buffer.\n\nThe buffer is zeroed on allocation, so a standalone request leaks\nnothing.  A compound request can leak: the offset of the next response\nis advanced by the length pinned for the previous one, so a reply that\nwas written into the buffer and then dropped in favour of the short\nerror response of smb2_set_err_rsp() stays there, and the next reply is\nlaid over it with only the header cleared.\n\nksmbd does not implement quota tracking, so report no control flags."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-28T10:34:31.576Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d8c450ad0d08980b39b08d435efa921086c8b227"
        },
        {
          "url": "https://git.kernel.org/stable/c/03bb4338c3a7c3fc4decf699a35753f0891aab2a"
        },
        {
          "url": "https://git.kernel.org/stable/c/c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e"
        }
      ],
      "title": "ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-99114",
    "datePublished": "2026-10-28T10:34:31.576Z",
    "dateReserved": "2026-09-25T10:25:14.392Z",
    "dateUpdated": "2026-10-28T10:34:31.576Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted