CVE-2026-98683: Linux kernel · smb: client: flush dirty data before zeroing a range
Source GCVE Database
Not known to be exploited · fixed in e8ba21c7e6ef3d4cb617858760673877b2e4a2bb : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e8ba21c7e6ef3d4cb617858760673877b2e4a2bb, cecf4114069fc19629d284710fd783d56bbca862, 8f8d32c1044f70e46e87550e039a15ff20a4b21c +3
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to unconditionally flush dirty data before zeroing a range in the SMB client code. Users should apply the official kernel update containing this fix once available. Since this is a kernel-level vulnerability, upgrading to the patched kernel version is the recommended remediation. No alternative mitigations are indicated.
Description
A vulnerability in the Linux kernel's SMB client implementation was resolved involving improper flushing of dirty data before zeroing a file range. The smb3_zero_range() function failed to flush dirty data for zero ranges that did not reach the end of the file, potentially causing stale data to be written back after zeroing. This could lead to reading stale data where zeroed data is expected. The issue was fixed by ensuring unconditional flushing of dirty data before zeroing, aligning with similar fixes in related code paths.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98683 (opens in a new tab)
- git.kernel.org/stable/c/8f8d32c1044f70e46e87550e039a15ff20a4b21c (opens in a new tab)
- git.kernel.org/stable/c/cecf4114069fc19629d284710fd783d56bbca862 (opens in a new tab)
- git.kernel.org/stable/c/e8ba21c7e6ef3d4cb617858760673877b2e4a2bb (opens in a new tab)