CVE-2026-99563: Linux kernel · smb: smbdirect: release failed pending sockets of a listener
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in df7e97ff4f114e1dc2188d11339b8d0299c4a77f : patch Linux kernel soon.
Data as of 19 Nov 2026, 15:04 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in df7e97ff4f114e1dc2188d11339b8d0299c4a77f, c13279523ed5da31ca7bba761115afdbd40e06eb, 328c7e307e8411899e2f90beae83da9e4c45d700
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 df7e97ff4f114e1dc2188d11339b8d0299c4a77f, c13279523ed5da31ca7bba761115afdbd40e06eb or 328c7e307e8411899e2f90beae83da9e4c45d700.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel. Users should update to a fixed kernel version containing the commits df7e97ff4f114e1dc2188d11339b8d0299c4a77f, c13279523ed5da31ca7bba761115afdbd40e06eb, or 328c7e307e8411899e2f90beae83da9e4c45d700. No additional mitigation is required once the kernel is updated.
Description
A vulnerability in the Linux kernel's SMB Direct (smbdirect) implementation allowed failed pending sockets of a listener to remain on the backlog list indefinitely. This caused new SMB-Direct connection attempts to be rejected with -EBUSY after the backlog limit was reached, enabling an unauthenticated peer to permanently block SMB-Direct connections. The issue has been fixed by properly orphaning and releasing failed sockets to prevent backlog exhaustion.