ntfs: treat any nonzero dio zero-range return as an error
- 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: treat any nonzero dio zero-range return as an error ntfs_dio_zero_range() returns either 0 or a negative errno from blkdev_issue_zeroout(); it never returns a positive value. The zeroing failure check in ntfs_attr_fallocate() therefore never fired, so a failed zeroing operation was silently ignored: the loop kept going, the newly allocated clusters were folded into initialized_size and the write could succeed leaving stale on-disk data. Treat any nonzero return as an error and abort the allocation.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 495e90fa334828d4119061e2726af51d0a0fb4ed · fixed in 56392b0d5290ff2b05fc673bc07803b8ae4cfd1b; From 495e90fa334828d4119061e2726af51d0a0fb4ed · fixed in 607a9478833db656e7ceac8e9e382fa4acfde545
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.7