CVE-2026-98683smb: client: flush dirty data before zeroing a range
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 23 days later
· 23 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 91d1dfae464987aaf6c79ff51d8674880fb3be77 – < 1506390a788c45af11008adc91a38dfb5beaf03c
- affected 91d1dfae464987aaf6c79ff51d8674880fb3be77 – < cecf4114069fc19629d284710fd783d56bbca862
- affected 91d1dfae464987aaf6c79ff51d8674880fb3be77 – < e8ba21c7e6ef3d4cb617858760673877b2e4a2bb
- affected 91d1dfae464987aaf6c79ff51d8674880fb3be77 – < 8f8d32c1044f70e46e87550e039a15ff20a4b21c
- affected 13af7446428771e9e529284d390e7994df8be683
- affected 0a9423f99ded38b32bd1864347332cc557e6b141
- affected 7dfa4279c55f467a88e653a5d544817181b22aea
- affected 6.1.110 – < 6.2
- affected 6.6.51 – < 6.7
- affected 6.10.10 – < 6.11
- affected 6.11
- unaffected < 6.11
- unaffected 6.12.117 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.10 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/1506390a788c45af11008adc91a38dfb5beaf03c (opens in a new tab)
- https://git.kernel.org/stable/c/cecf4114069fc19629d284710fd783d56bbca862 (opens in a new tab)
- https://git.kernel.org/stable/c/e8ba21c7e6ef3d4cb617858760673877b2e4a2bb (opens in a new tab)
- https://git.kernel.org/stable/c/8f8d32c1044f70e46e87550e039a15ff20a4b21c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103937 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98683)Record last updated .