GHSA-PM9X-9FFX-JRQJ
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In the Linux kernel, the following vulnerability has been resolved:
ntfs: treat any nonzero dio zero-range return as an error
ntfs_dio_zero_range() returns either 0 or a negative errno from blkdev_issue_zeroout(); it never returns a positive value. The zeroing failure check in ntfs_attr_fallocate() therefore never fired, so a failed zeroing operation was silently ignored: the loop kept going, the newly allocated clusters were folded into initialized_size and the write could succeed leaving stale on-disk data.
Treat any nonzero return as an error and abort the allocation.
{
"affected": [],
"aliases": [
"CVE-2026-98137"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:45Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: treat any nonzero dio zero-range return as an error\n\nntfs_dio_zero_range() returns either 0 or a negative errno from\nblkdev_issue_zeroout(); it never returns a positive value. The\nzeroing failure check in ntfs_attr_fallocate() therefore never fired,\nso a failed zeroing operation was silently ignored: the loop kept\ngoing, the newly allocated clusters were folded into initialized_size\nand the write could succeed leaving stale on-disk data.\n\nTreat any nonzero return as an error and abort the allocation.",
"id": "GHSA-pm9x-9ffx-jrqj",
"modified": "2026-09-25T12:31:38Z",
"published": "2026-09-25T12:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98137"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/56392b0d5290ff2b05fc673bc07803b8ae4cfd1b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/607a9478833db656e7ceac8e9e382fa4acfde545"
}
],
"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.