GHSA-X5P7-QJX7-H5J9
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix uninitialized return value in netfs_unbuffered_write()
If preparation of the first subrequest fails, netfs_unbuffered_write() exits its loop before ret is initialized. The empty-iterator check can do the same.
For synchronous writes, netfs_unbuffered_write_iter_locked() may then return an unrelated error instead of wreq->error. This is reachable through CIFS if cifs_prepare_write() fails to reopen the file or obtain credits.
Initialize ret to 0 so the caller returns wreq->error if no data was written, or the number of bytes already written otherwise.
Found with Clang's -Wconditional-uninitialized.
{
"affected": [],
"aliases": [
"CVE-2026-97610"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:15Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix uninitialized return value in netfs_unbuffered_write()\n\nIf preparation of the first subrequest fails,\nnetfs_unbuffered_write() exits its loop before ret is initialized. The\nempty-iterator check can do the same.\n\nFor synchronous writes, netfs_unbuffered_write_iter_locked() may then\nreturn an unrelated error instead of wreq-\u003eerror. This is reachable\nthrough CIFS if cifs_prepare_write() fails to reopen the file or obtain\ncredits.\n\nInitialize ret to 0 so the caller returns wreq-\u003eerror if no data was\nwritten, or the number of bytes already written otherwise.\n\nFound with Clang\u0027s -Wconditional-uninitialized.",
"id": "GHSA-x5p7-qjx7-h5j9",
"modified": "2026-09-25T12:31:26Z",
"published": "2026-09-25T12:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97610"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2e38d500471d097cda87d7d374bbc1b13493075d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3d038eebdbd400c3bc4b66bd8aa0dff0c2bcce26"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f18e8774f4d3137fa0a5fb8ffa83d59a719666d8"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.