CVE-2026-98683

smb: client: flush dirty data before zeroing a range

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: flush dirty data before zeroing a range smb3_zero_range() emulates FALLOC_FL_ZERO_RANGE by invalidating the page cache over the target range with truncate_pagecache_range() and then issuing FSCTL_SET_ZERO_DATA to the server. Dirty data was only flushed conditionally, when the range reached or extended EOF. For a purely interior zero range that does not reach EOF, no flush happened, so a dirty folio overlapping the range could be written back to the server after the FSCTL and refill the range that was just zeroed with stale data. Fix this by unconditionally flushing and waiting for dirty data in the range before invalidating the page cache and issuing FSCTL_SET_ZERO_DATA, exactly as was done for smb3_punch_hole() in commit d7d2adcd022b ("smb/client: flush dirty data before punching a hole"); the two paths are structurally identical here. This is observed as generic/363 randomly reading stale data where a zeroed range is expected against Windows Server.

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
  • 91d1dfae464987aaf6c79ff51d8674880fb3be77 up to but excluding 1506390a788c45af11008adc91a38dfb5beaf03c (affected)
  • 91d1dfae464987aaf6c79ff51d8674880fb3be77 up to but excluding cecf4114069fc19629d284710fd783d56bbca862 (affected)
  • 91d1dfae464987aaf6c79ff51d8674880fb3be77 up to but excluding e8ba21c7e6ef3d4cb617858760673877b2e4a2bb (affected)
  • 91d1dfae464987aaf6c79ff51d8674880fb3be77 up to but excluding 8f8d32c1044f70e46e87550e039a15ff20a4b21c (affected)
  • 13af7446428771e9e529284d390e7994df8be683 (affected)
  • 0a9423f99ded38b32bd1864347332cc557e6b141 (affected)
  • 7dfa4279c55f467a88e653a5d544817181b22aea (affected)
  • 6.1.110 up to but excluding 6.2 (affected)
  • 6.6.51 up to but excluding 6.7 (affected)
  • 6.10.10 up to but excluding 6.11 (affected)
LinuxLinux
  • Default status: affected
  • 6.11 (affected)
  • 0 up to but excluding 6.11 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 6.18.56 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