VulnerabilityPublished 23 Oct 2026

CVE-2026-99008: Linux kernel · Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown

Source GCVE Database

Authoritative record:CVE-2026-99008· Medium

Not known to be exploited · fixed in d5c372ad03330f02962d4860df4d355ab25487df : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Medium

Rated by Threat Radar · 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-5xf6-vj9w-8fx6

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ cad348a17e170451ea8688b532a6ca3e98c63b60, < d5c372ad03330f02962d4860df4d355ab25487df	Fixed in d5c372ad03330f02962d4860df4d355ab25487df
LinuxLinux	Affected ≥ cad348a17e170451ea8688b532a6ca3e98c63b60, < d0aef0b0374678153244f162df507106d728af39	Fixed in d0aef0b0374678153244f162df507106d728af39
LinuxLinux	Affected ≥ cad348a17e170451ea8688b532a6ca3e98c63b60, < a661f401f83b8462f2d424e0a1a72b7681e92ea2	Fixed in a661f401f83b8462f2d424e0a1a72b7681e92ea2
LinuxLinux	Affected ≥ cad348a17e170451ea8688b532a6ca3e98c63b60, < 08e90633377f1b2567ab5ad6810b74c552246a07	Fixed in 08e90633377f1b2567ab5ad6810b74c552246a07
LinuxLinux	Affected ≥ cad348a17e170451ea8688b532a6ca3e98c63b60, < 3fd5164bdb04635caa7942ddb554b0ec699a9433	Fixed in 3fd5164bdb04635caa7942ddb554b0ec699a9433
LinuxLinux	Affected =3.12	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed. rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev->tty_dev. If that registration fails, dev->tty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev->tty_dev without checking it: Oops: general protection fault, probably for non-canonical address KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047] RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131 Call Trace: tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372 tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705 tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718 __fput+0x418/0xa50 fs/file_table.c:512 rfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.

References

Community reviews

Loading reviews…