ntfs: protect runlist updates with the runlist lock
- 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.8
- 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: protect runlist updates with the runlist lock ntfs_non_resident_attr_shrink() calls runlist helpers that require the runlist write lock, but did not hold it while freeing clusters and truncating the runlist. Serialize those operations and the resident conversion with the runlist lock. ntfs_attr_map_cluster() can merge a newly allocated run before updating mapping pairs. If the update fails, free the clusters and restore both the in-memory runlist and on-disk mapping pairs from a saved runlist. Mark the volume in error if either rollback step fails.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 495e90fa334828d4119061e2726af51d0a0fb4ed · fixed in 742797432e8c9b0dd54ecc523c185e26b09d79a0; From 495e90fa334828d4119061e2726af51d0a0fb4ed · fixed in 91709ba5d6d709b2b663287b7e871e2c6b480502
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.8