VulnWatch by ve1ve2
unknown EPSS 0.17%

DEBIAN-CVE-2026-98682: In the Linux kernel, the following vulnerability has been resolved: smb: client: drain and invalidate before server-side copy/clone cifs_file_copychunk_range()…

Source:
OSV.dev
Published:
Fetched:
Updated:
Affects:
linux 12:linux

https://osv.dev/vulnerability/DEBIAN-CVE-2026-98682 ↗

osvdebianfix-available

In the Linux kernel, the following vulnerability has been resolved: smb: client: drain and invalidate before server-side copy/clone cifs_file_copychunk_range() and the clone (FICLONE) path of cifs_remap_file_range() do not serialise the destination page cache against the server-side copy the way the other server-side range operations (smb3_zero_range(), smb3_punch_hole(), smb3_collapse_range() and smb3_insert_range()) do. cifs_file_copychunk_range() invalidates the destination range with filemap_invalidate_inode(), which takes and drops the mapping's invalidate_lock internally, so the lock is no longer held when the copychunk ioctl is issued. It also never drains in-flight netfs I/O on the target. The clone path never takes the invalidate_lock at all (only i_rwsem), uses a bare truncate_inode_pages_range() and likewise does not drain outstanding I/O. As a result an asynchronous destination writeback can complete after the server-side copy/clone has run and reinstate stale data over the region just written by the server, corrupting the file. This is the same class of corruption as commit d7d2adcd022b ("smb/client: flush dirty data before punching a hole") and has been seen randomly in generic/363 against Windows Server. Fix both paths to follow the established ordering: hold the target mapping's invalidate_lock across the flush and invalidation of the destination and the server ioctl, and call netfs_wait_for_outstanding_io() on the target to drain in-flight writes before the ioctl is issued. Only the target inode's invalidate_lock is required, as the source is merely flushed and not invalidated; i_rwsem (already held via lock_two_nondirectories()) is acquired before the invalidate_lock, matching the VFS lock ordering. Since filemap_invalidate_inode() takes that same lock internally, replace it with its own unmap/flush/invalidate steps instead of calling it, and return early on a zero-length copy to avoid a range underflow. Affected: Debian:12:linux, Debian:12:linux-6.12, Debian:13:linux, Debian:14:linux Fixed in: 6.12.117-1, 7.2.10-1, 6.12.117-1~deb12u1 References: https://security-tracker.debian.org/tracker/CVE-2026-98682

Linked vulnerabilities (1)

CVE-2026-98682 unknown EPSS 0.17% (p6) NVDCVE.org

In the Linux kernel, the following vulnerability has been resolved: smb: client: drain and invalidate before server-side copy/clone cifs_file_copychunk_range() and the clone (FICLONE) path of cifs_remap_file_range() do not serialise the destination page cache against the server-side copy the way the other server-side range operations (smb3_zero_range(), smb3_punch_hole(), smb3_collapse_range() and smb3_insert_range()) do. cifs_file_copychunk_range() invalidates the destination range with filemap_invalidate_inode(), which takes and drops the mapping's invalidate_lock internally, so the...

Aliases: CVE-2026-100080, CVE-2026-100081, CVE-2026-100082, CVE-2026-89866, CVE-2026-92499, CVE-2026-98176, CVE-2026-98177, CVE-2026-98180, CVE-2026-98228, CVE-2026-98408, CVE-2026-98439, CVE-2026-98449, CVE-2026-98466, CVE-2026-98674, CVE-2026-98683, CVE-2026-98684, CVE-2026-98685, CVE-2026-98714, CVE-2026-98715, CVE-2026-98786, CVE-2026-98853, CVE-2026-98863, CVE-2026-98920, CVE-2026-98978, CVE-2026-98989, CVE-2026-98996, CVE-2026-99021, CVE-2026-99026, CVE-2026-99076, CVE-2026-99086, CVE-2026-99087, CVE-2026-99109, CVE-2026-99122, CVE-2026-99146, CVE-2026-99172, CVE-2026-99270, CVE-2026-99271, CVE-2026-99273, CVE-2026-99274, CVE-2026-99281, CVE-2026-99282, CVE-2026-99283, CVE-2026-99286, CVE-2026-99287, CVE-2026-99288, CVE-2026-99290, CVE-2026-99292, CVE-2026-99295, CVE-2026-99296NVD: Received