CVE-2026-99008

Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown

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.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.177% likely to be exploited in the next 30 days, higher than 7.374% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding b2b915042be073637d9f93dc51ef15fc0685ae8a (affected)
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding a43452d8c1015ac2f0e43ff946be5425427b02cc (affected)
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding 3f6394f6c6d1b6817065d3b402f55d437063a704 (affected)
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding d5c372ad03330f02962d4860df4d355ab25487df (affected)
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding 3fd5164bdb04635caa7942ddb554b0ec699a9433 (affected)
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding a661f401f83b8462f2d424e0a1a72b7681e92ea2 (affected)
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding d0aef0b0374678153244f162df507106d728af39 (affected)
  • cad348a17e170451ea8688b532a6ca3e98c63b60 up to but excluding 08e90633377f1b2567ab5ad6810b74c552246a07 (affected)
LinuxLinux
  • Default status: affected
  • 3.12 (affected)
  • 0 up to but excluding 3.12 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References