CVE-2026-99534: Linux kernel · ksmbd: prevent stale data from being written by SMB2 WRITE requests
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fbe9fcda7ae8835b454c376de1d49232ab6bbcfb : update Linux kernel when convenient.
Data as of 19 Nov 2026, 15:19 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fbe9fcda7ae8835b454c376de1d49232ab6bbcfb, bc0e0f5ac1d7b044d403f859406b4b66d4b1ce9b, 139e8a3d6edd0c5b5dfe4ada2f636146e1209dc3 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 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
This vulnerability has been fixed in Linux kernel versions 5.16, 6.2, and 6.4 and their respective stable updates. Users and administrators should upgrade to these fixed versions or later to mitigate the issue. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's ksmbd component could cause stale data to be written by SMB2 WRITE requests. The issue arises from improper initialization of the compatibility byte in request buffers, which may lead to stale request-buffer data being written to files or sent to IPC pipes. The flaw has been addressed by initializing the compatibility byte without zeroing the entire allocation and validating the data range in WRITE handlers against the current compound request.
References
- git.kernel.org/stable/c/139e8a3d6edd0c5b5dfe4ada2f636146e1209dc3 (opens in a new tab)
- git.kernel.org/stable/c/fbe9fcda7ae8835b454c376de1d49232ab6bbcfb (opens in a new tab)
- git.kernel.org/stable/c/97d489f68b85a5b64496e01d4cb3c0e092aa817e (opens in a new tab)
- git.kernel.org/stable/c/bc0e0f5ac1d7b044d403f859406b4b66d4b1ce9b (opens in a new tab)