GHSA-X7VM-8XFR-C29X
Vulnerability from github – Published: 2026-11-19 15:31 – Updated: 2026-11-19 15:31In the Linux kernel, the following vulnerability has been resolved:
ksmbd: preserve unreadable named streams on open
A write-only client can open an existing named stream with FILE_OPEN_IF without permission to read the underlying file. The case-insensitive lookup finds the xattr name, but querying its value length then fails with -EACCES. smb2_set_stream_name_xattr() treats every negative result as a missing stream and replaces the existing xattr with an empty value.
A failed xattr list is not proof that the stream is absent either: for example, -ENOMEM can lead to the same empty replacement. Preserve listing errors and create a stream only for -ENOENT or -ENODATA. The latter can occur if the xattr is removed between listing its name and querying its value. Return other lookup errors without changing the stream.
A write-only FILE_OPEN now reports access denied instead of name not found. FILE_OVERWRITE_IF and FILE_SUPERSEDE on an unreadable stream also fail instead of appearing to replace it. Stream writes and EOF changes already need to read the old value, so such handles cannot update the stream after opening either.
{
"affected": [],
"aliases": [
"CVE-2026-99537"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T15:18:09Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: preserve unreadable named streams on open\n\nA write-only client can open an existing named stream with FILE_OPEN_IF\nwithout permission to read the underlying file. The case-insensitive\nlookup finds the xattr name, but querying its value length then fails\nwith -EACCES. smb2_set_stream_name_xattr() treats every negative result\nas a missing stream and replaces the existing xattr with an empty value.\n\nA failed xattr list is not proof that the stream is absent either:\nfor example, -ENOMEM can lead to the same empty replacement. Preserve\nlisting errors and create a stream only for -ENOENT or -ENODATA. The\nlatter can occur if the xattr is removed between listing its name and\nquerying its value. Return other lookup errors without changing the\nstream.\n\nA write-only FILE_OPEN now reports access denied instead of name not\nfound. FILE_OVERWRITE_IF and FILE_SUPERSEDE on an unreadable stream\nalso fail instead of appearing to replace it. Stream writes and EOF\nchanges already need to read the old value, so such handles cannot\nupdate the stream after opening either.",
"id": "GHSA-x7vm-8xfr-c29x",
"modified": "2026-11-19T15:31:27Z",
"published": "2026-11-19T15:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99537"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/22464634d240f5132b0787048a10e8260ac7e639"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4cdee894f9bcebe0093df90cf28dc732d38418da"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/80c816c047f7cae3c99cc75740c1f5d2c4d97b45"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f5f6a705247314540b780dbf94c319d764b84bb4"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.