GHSA-4M2C-P8VW-33GR
Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31In the Linux kernel, the following vulnerability has been resolved:
cifs: don't update i_size in cifs_do_truncate without a cached handle
If find_writable_file() returns null, cifs_file_flush will return 0 without issuing set_file_size, and the outer 'if (!rc)' block will set i_size to 0 before telling the server to truncate. If the cifs_open() then fails, the inode will have size 0, while the server file is unchanged.
Move the netfs_resize_file() and cifs_setsize() into the 'if (cfile)', so they only run after a successful set_file_size.
In the no-handle else branch, evict stale pages with truncate_inode_pages before the O_TRUNC open to dispose of old cache pages, and let the open response set the i_size.
{
"affected": [],
"aliases": [
"CVE-2026-99137"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-28T11:17:33Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncifs: don\u0027t update i_size in cifs_do_truncate without a cached handle\n\nIf find_writable_file() returns null, cifs_file_flush will return\n0 without issuing set_file_size, and the outer \u0027if (!rc)\u0027 block\nwill set i_size to 0 before telling the server to truncate. If\nthe cifs_open() then fails, the inode will have size 0, while\nthe server file is unchanged.\n\nMove the netfs_resize_file() and cifs_setsize() into the \u0027if\n(cfile)\u0027, so they only run after a successful set_file_size.\n\nIn the no-handle else branch, evict stale pages with\ntruncate_inode_pages before the O_TRUNC open to dispose of old\ncache pages, and let the open response set the i_size.",
"id": "GHSA-4m2c-p8vw-33gr",
"modified": "2026-10-28T12:31:04Z",
"published": "2026-10-28T12:31:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99137"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/04d020b3d0b58a1b7e116900e4095b96a7f4e11a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/88a51743cd8094b76fd910f53f718747c7729cc8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fe39cd9d48f2346605f3746e0cc19e89d5f373eb"
}
],
"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
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.