CVE Intelligence
Unknown

CVE-2026-99008 — Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown

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.

Published Oct 23, 2026 · Updated Oct 30, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.17%
ahead of 6% of scored CVEs · Oct 30, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < d5c372ad03330f02962d4860df4d355ab25487df≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < 3fd5164bdb04635caa7942ddb554b0ec699a9433≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < a661f401f83b8462f2d424e0a1a72b7681e92ea2≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < d0aef0b0374678153244f162df507106d728af39≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < 08e90633377f1b2567ab5ad6810b74c552246a07version 3.12≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < b2b915042be073637d9f93dc51ef15fc0685ae8a≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < a43452d8c1015ac2f0e43ff946be5425427b02cc
and 1 more ≥ cad348a17e170451ea8688b532a6ca3e98c63b60 and < 3f6394f6c6d1b6817065d3b402f55d437063a704
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 30, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 23, 2026
  • Affected products added · linux/linux
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 23, 2026 · Alertas do Telegram
  • CVE published
    Oct 23, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 23, 2026 – Oct 30, 2026
  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

10 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
  • CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
  • CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
  • CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
  • CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
  • CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-99008 is "Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.