ntfs: do not mark the volume clean in sync_fs when errors were recorded
- 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: do not mark the volume clean in sync_fs when errors were recorded ntfs_put_super() and the remount-read-only path both clear the dirty bit only when NVolErrors(vol) is false. ntfs_sync_fs() clears it unconditionally, so any sync() on a volume that recorded an error marks that volume clean. A volume without this set is then seen as not needing recovery and it does not run one, so whatever went wrong is never repaired. This change skips resetting the dirty bit when there are volume errors. Reproduced on a volume whose $MFTMirr does not match $MFT, which sets the error flag while leaving the mount read-write: after a write and a sync, the on-disk volume flags read 0x0000 with this driver and 0x0001 with the guard in place.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6251f0b0de7d645e3591931ca4c11d8322c1866f · fixed in ca1f9933eff777a604eb664d0f9ae433b8664cbf; From 6251f0b0de7d645e3591931ca4c11d8322c1866f · fixed in 0e4c839905418d55bafe571a92533a1d1ac7b0a8
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.7