CVE-2026-99008: Linux kernel · Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:58 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10linuxpkg:deb/ubuntu/linux?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-oraclepkg:deb/ubuntu/linux-oracle?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available that adds a NULL check in rfcomm_dev_shutdown() to prevent dereferencing a NULL tty_dev pointer. Users should apply the updated Linux kernel versions that include this patch to remediate the issue.
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. The fix adds a check to ensure the tty device pointer is valid before use.
References
- ubuntu.com/security/CVE-2026-99008 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-99008 (opens in a new tab)
- git.kernel.org/stable/c/08e90633377f1b2567ab5ad6810b74c552246a07 (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/d5c372ad03330f02962d4860df4d355ab25487df (opens in a new tab)