CVE-2026-99536: Linux kernel · ksmbd: prevent session binding in compound requests
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 19f8fd6b5ced33b02a083759e6901f9d6e8076df : 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 19f8fd6b5ced33b02a083759e6901f9d6e8076df, 7.2, 4f148586c9cb18ad47b5f41153139d0fefa596d3
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 Linux kernel to 19f8fd6b5ced33b02a083759e6901f9d6e8076df, 7.2 or 4f148586c9cb18ad47b5f41153139d0fefa596d3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel version 7.2 and the specified commit versions. Users and administrators should update to Linux kernel 7.2 or later to remediate this issue. No additional mitigation steps are indicated or required beyond applying the official fix.
Description
A vulnerability in the Linux kernel's ksmbd component allowed session binding in compound SMB2 requests, which could cause a failed multichannel binding to retain its target session improperly. This flaw could lead to subsequent compound commands reusing that session along with a leftover tree connection, potentially causing incorrect session handling. The issue has been fixed by limiting SESSION_SETUP binding requests to standalone messages during validation, preventing session replacement in compound requests.