Live › vulnerability › CVE-2026-98685
Go to dashboardIn the Linux kernel's SMB client, a file clone that extends a file could leave stale data from beyond the old end of file in the page cache, and that data became visible as file content after the extension. The sources do not state a confirmed attacker-controlled impact beyond this data exposure.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the CIFS/SMB client and mounted SMB shares that use clone range (reflink-style remap) operations on files that were modified through mmap. Systems without SMB mounts are unlikely to be affected. The sources do not give more detail.
No product ranges from the sources yet.
uname -r and compare against the kernel version that contains the upstream fix, which the sources do not name.mount -t cifs or findmnt -t cifs.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98685")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.