CVE-2026-99008: Linux kernel · Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d5c372ad03330f02962d4860df4d355ab25487df : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d5c372ad03330f02962d4860df4d355ab25487df, d0aef0b0374678153244f162df507106d728af39, a661f401f83b8462f2d424e0a1a72b7681e92ea2 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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
|
| 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 a fixed kernel version that includes the patch identified by the commits listed in establishedFacts.fixedVersions. No additional mitigation is required once patched.
Description
A NULL pointer dereference vulnerability in the Linux kernel's Bluetooth RFCOMM subsystem was fixed. The issue occurs in the rfcomm_dev_shutdown function when closing an RFCOMM tty device that was never fully registered, leading to a NULL dereference and kernel crash.
References
- git.kernel.org/stable/c/d5c372ad03330f02962d4860df4d355ab25487df (opens in a new tab)
- git.kernel.org/stable/c/3fd5164bdb04635caa7942ddb554b0ec699a9433 (opens in a new tab)
- git.kernel.org/stable/c/a661f401f83b8462f2d424e0a1a72b7681e92ea2 (opens in a new tab)
- git.kernel.org/stable/c/d0aef0b0374678153244f162df507106d728af39 (opens in a new tab)
- git.kernel.org/stable/c/08e90633377f1b2567ab5ad6810b74c552246a07 (opens in a new tab)