smb: client: discard post-EOF pagecache when extending a file via clone 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.2, 6.7, 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 clone range cifs_remap_file_range() discarded the pagecache only for the folios overlapping the destination region, so when a clone 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. Start the discard at the smaller of fstart and the old EOF. i_size is still old here, so nothing past the old EOF is flushed to the server.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From c54fc3a4f375663f2361a9cbb2955fb4ef912879 · fixed in 15bb9f1d3e967e328649e92a1451e60a0dc66118; From c54fc3a4f375663f2361a9cbb2955fb4ef912879 · fixed in 4721587f96cb8de8164f3fd203093a0875560999; From 6.1.68 · fixed in 6.2; From 6.6.7 · fixed in 6.7
- Linux Linux
6.7
- KernelLinux
From 6.7.0 · fixed in 7.2.10