Vulnerability Description
In 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 7.1, < 7.2.7 |
References
- https://git.kernel.org/stable/c/7eb97d8828e7758b9c81277f7802e740a800f78aPatch
- https://git.kernel.org/stable/c/be9e89ccb8e52a3e4b67feeb03ebd8133091dc7ePatch
FAQ
What is CVE-2026-98139?
CVE-2026-98139 is a vulnerability with a CVSS score of 5.5 (MEDIUM). In 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_free...
How severe is CVE-2026-98139?
CVE-2026-98139 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-98139?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.