ntfs: only count successfully cleared runs when freeing clusters
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 11ccc9107dc460de28af90fac1f42404d9802735 · fixed in 7eb97d8828e7758b9c81277f7802e740a800f78a; From 11ccc9107dc460de28af90fac1f42404d9802735 · fixed in be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.7