CVE-2026-99793: Linux kernel · Bluetooth: L2CAP: Only accept connection responses to outstanding requests
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c6789ceaf6e28e97d73434e12c7ae60432f86dbb : patch Linux kernel soon.
Data as of 20 Nov 2026, 06:06 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 c6789ceaf6e28e97d73434e12c7ae60432f86dbb, bef1f610bc1f99b349368cb8d9025c2ff66d1fbe, a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 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 19 Nov 2026.
What to do
Upgrade Linux kernel to c6789ceaf6e28e97d73434e12c7ae60432f86dbb, bef1f610bc1f99b349368cb8d9025c2ff66d1fbe, a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 or 08ad7b94a31820eb3082851b924f76503fe66ebf.
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
This vulnerability has been fixed in the Linux kernel. Users should update to the fixed versions identified by the commits c6789ceaf6e28e97d73434e12c7ae60432f86dbb, bef1f610bc1f99b349368cb8d9025c2ff66d1fbe, a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9, and 08ad7b94a31820eb3082851b924f76503fe66ebf. No additional mitigation is required.
Description
A vulnerability in the Linux kernel Bluetooth L2CAP implementation allowed connection responses to be accepted before security procedures completed, potentially leaving a channel connected without the required security level. This flaw was fixed by ensuring connection responses are only accepted for outstanding requests and properly matched by identifier.
References
- git.kernel.org/stable/c/08ad7b94a31820eb3082851b924f76503fe66ebf (opens in a new tab)
- git.kernel.org/stable/c/c6789ceaf6e28e97d73434e12c7ae60432f86dbb (opens in a new tab)
- git.kernel.org/stable/c/bef1f610bc1f99b349368cb8d9025c2ff66d1fbe (opens in a new tab)
- git.kernel.org/stable/c/a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 (opens in a new tab)