CVE-2026-98682

smb: client: drain and invalidate before server-side copy/clone

Description

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.

Key facts

Published
18 Oct 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.102% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • c54fc3a4f375663f2361a9cbb2955fb4ef912879 up to but excluding 6e7a06704457594f06e4ea58a17a5d162ccc735c (affected)
  • c54fc3a4f375663f2361a9cbb2955fb4ef912879 up to but excluding e97dac26ed2cce04f9d159cc99e1eca828c5d49e (affected)
  • c54fc3a4f375663f2361a9cbb2955fb4ef912879 up to but excluding dc71660f11ef2fecc0695a41e49cd496a9d255ab (affected)
  • c54fc3a4f375663f2361a9cbb2955fb4ef912879 up to but excluding c9b1194e8ec99d95db25db45edd2fbf690f043ab (affected)
  • 358bd5f436d820bb758833050aae065b35d6986c (affected)
  • 43801359c8971cc49b4a4db5015fba77fbd09c32 (affected)
  • 6.1.68 up to but excluding 6.2 (affected)
  • 6.6.7 up to but excluding 6.7 (affected)
LinuxLinux
  • Default status: affected
  • 6.7 (affected)
  • 0 up to but excluding 6.7 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 6.18.61 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References