GHSA-6RPR-WQMR-68RH
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: only count successfully cleared runs when freeing clusters
ntfs_cluster_free_from_rl_nolock() adds a run's length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol->free_clusters, corrupting statfs output and the allocator's free space gate.
Only count runs whose bitmap clear succeeded.
{
"affected": [],
"aliases": [
"CVE-2026-98139"
],
"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: only count successfully cleared runs when freeing clusters\n\nntfs_cluster_free_from_rl_nolock() adds a run\u0027s length to nr_freed\nwhenever the error bookkeeping condition is false, which includes\ncases where ntfs_bitmap_clear_run() actually failed - e.g. a second\nrun failing with the same errno as an earlier one, or any failure\nafter a non-ENOMEM error was already recorded. Since a failed\nntfs_bitmap_clear_run() rolls back its partial modifications, no\nbits were cleared for that run, yet its length still inflates\nvol-\u003efree_clusters, corrupting statfs output and the allocator\u0027s\nfree space gate.\n\nOnly count runs whose bitmap clear succeeded.",
"id": "GHSA-6rpr-wqmr-68rh",
"modified": "2026-09-25T12:31:38Z",
"published": "2026-09-25T12:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98139"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7eb97d8828e7758b9c81277f7802e740a800f78a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e"
}
],
"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.