Answer in brief
CVE-2026-99008 records a Unknown severity vulnerability in Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cad348a17e170451ea8688b532a6ca3e98c63b60 <d5c372ad03330f02962d4860df4d355ab25487df || >=cad348a17e170451ea8688b532a6ca3e98c63b60 <3fd5164bdb04635caa7942ddb554b0ec699a9433 || >=cad348a17e170451ea8688b532a6ca3e98c63b60 <a661f401f83b8462f2d424e0a1a72b7681e92ea2 || >=cad348a17e170451ea8688b532a6ca3e98c63b60 <d0aef0b0374678153244f162df507106d728af39 || >=cad348a17e170451ea8688b532a6ca3e98c63b60 <08e90633377f1b2567ab5ad6810b74c552246a07 | d5c372ad03330f02962d4860df4d355ab25487df, 3fd5164bdb04635caa7942ddb554b0ec699a9433, a661f401f83b8462f2d424e0a1a72b7681e92ea2, d0aef0b0374678153244f162df507106d728af39, 08e90633377f1b2567ab5ad6810b74c552246a07 |
| Linux/Linuxgeneric | 3.12 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.