smb: client: discard post-EOF pagecache when extending a file via zero range
- 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 6.6.160, 6.12.113, 6.18.56, 7.2.10
- 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: smb: client: discard post-EOF pagecache when extending a file via zero range smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended. Lower the discard boundary to the smaller of the zero-range offset and the old EOF.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 72c419d9b073628d3b5b0b2fc787b724f1a8c726 · fixed in 3df27277f8f95345d4a6c57367824bf1aefdbf66; From 72c419d9b073628d3b5b0b2fc787b724f1a8c726 · fixed in 94949b6b2f2bf0dba2e8786aed0b08cc6bc3a183; From 72c419d9b073628d3b5b0b2fc787b724f1a8c726 · fixed in b75dadb50a25eed525264bf6fea44fad94e7626f; From 72c419d9b073628d3b5b0b2fc787b724f1a8c726 · fixed in 6a8279c98ad289b27c0bdb11adb3f0c0b7fd456d; From 72c419d9b073628d3b5b0b2fc787b724f1a8c726 · fixed in da4fe97fb6c730d9c94a115c7bfa6f98e0d578d0
- Linux Linux
5.1
- KernelLinux
From 5.1.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10