CVE-2026-99538: Linux kernel · ksmbd: ignore network devices of other namespaces
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ddbcb0fe1b4ae5fd2c85fba5be61af1a554fce3b : 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 ddbcb0fe1b4ae5fd2c85fba5be61af1a554fce3b, cd27b2436d7fd04aaa8166ff3ce0da74cb12fe49, 9582dc3a31784ac930293b15edaa36c897d74e27 +1
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 ddbcb0fe1b4ae5fd2c85fba5be61af1a554fce3b, cd27b2436d7fd04aaa8166ff3ce0da74cb12fe49, 9582dc3a31784ac930293b15edaa36c897d74e27 or 1f5ce2b8b9164b3fcb93a18fe1e7b451c2fc6eea.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to the fixed kernel versions identified by the commits ddbcb0fe1b4ae5fd2c85fba5be61af1a554fce3b, cd27b2436d7fd04aaa8166ff3ce0da74cb12fe49, 9582dc3a31784ac930293b15edaa36c897d74e27, and 1f5ce2b8b9164b3fcb93a18fe1e7b451c2fc6eea to resolve this issue.
Description
A vulnerability in the Linux kernel's ksmbd component causes it to bind network devices across different network namespaces incorrectly. This leads to conflicts where SMB servers inside containers fail to start due to address conflicts, and network events in one namespace can inadvertently affect listeners in another. The issue is resolved by restricting ksmbd to handle network device events only in the initial network namespace.
References
- git.kernel.org/stable/c/cd27b2436d7fd04aaa8166ff3ce0da74cb12fe49 (opens in a new tab)
- git.kernel.org/stable/c/9582dc3a31784ac930293b15edaa36c897d74e27 (opens in a new tab)
- git.kernel.org/stable/c/ddbcb0fe1b4ae5fd2c85fba5be61af1a554fce3b (opens in a new tab)
- git.kernel.org/stable/c/1f5ce2b8b9164b3fcb93a18fe1e7b451c2fc6eea (opens in a new tab)