Read the docs
TI-2026-64374 Aliases CVE-2026-97975GHSA-2vfm-8xc8-7w2c

Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del()

Priority LOW 22Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Partial Red Hat: 5 without a fix

No CVSS vector from any source. Fix status from CNA and Red Hat.

Summary

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() A NULL pointer dereference in klist_put() occurs when a child device (such as a BNEP network device in bnep_session) is concurrently being unregistered while hci_conn_del_sysfs() reparents child devices. This is caused by a race condition between hci_conn_del_sysfs() and concurrent child device unregistration (e.g. bnep_session calling unregister_netdev()). During device unregistration, device_del() snapshots a non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the child device using device_find_any_child() and calls device_move() to reparent it to NULL, which removes the node from its parent's klist and clears knode_parent. Subsequently, device_del() calls klist_del(&dev->p->knode_parent) using the stale parent snapshot, causing klist_put() to dereference knode_klist(n)->put on an already removed node, resulting in a NULL pointer dereference. This race was introduced by commit 27aabf27fd01 ("Bluetooth: fix use-after-free in device_for_each_child()"), which replaced device_find_child(..., __match_tty) with device_find_any_child() in hci_conn_del_sysfs(). That change was intended to avoid a use-after-free where conn->dev outlived its parent hdev->dev when child devices held references to conn->dev, because conn->dev only held a reference to hdev->dev while registered in sysfs. Fix the issue properly by taking an explicit reference to the parent device with get_device(&hdev->dev) in hci_conn_init_sysfs() and dropping it with put_device(parent) in bt_link_release() when the conn device is freed. This ensures that hdev->dev remains valid for the entire lifecycle of conn->dev, resolving the underlying use-after-free. With the parent reference held properly, restore the __match_tty filter in hci_conn_del_sysfs() so that device_move() is only invoked on persistent RFCOMM TTY devices as originally intended, eliminating the race condition with unregistering network devices.

Why it matters now

EPSS 0.00168 6th percentileScored 2026-11-07
Fix Partial Linux (Linux): 6.6.160, 6.12.114, 5.5 +7Red Hat: 5 without a fix

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux6.6.64 to before 6.6.160; 6.12.2 to before 6.12.114; 5.4.297 to before 5.5; 5.10.231 to before 5.11; 5.15.174 to before 5.16; 6.1.120 to before 6.2; 6.11.11 to before 6.126.6.160, 6.12.114, 5.5, 5.11, 5.16, 6.2, 6.12Patch availableCNA
LinuxLinux6.13 and later6.6.160, 6.12.114, 6.18.53, 7.2.7, 7.3Patch availableCNA
  • Linux VendorLinux Affected 6.6.64 to before 6.6.160; 6.12.2 to before 6.12.114; 5.4.297 to before 5.5; 5.10.231 to before 5.11; 5.15.174 to before 5.16; 6.1.120 to before 6.2; 6.11.11 to before 6.12 Fixed in 6.6.160, 6.12.114, 5.5, 5.11, 5.16, 6.2, 6.12 Patch available CNA
  • Linux VendorLinux Affected 6.13 and later Fixed in 6.6.160, 6.12.114, 6.18.53, 7.2.7, 7.3 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*——Linux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions — — ·Linux

Remediation

  • Fix · CNA Linux (Linux) Fixed in 6.6.160, 6.12.114, 5.5, 5.11, 5.16, 6.2, 6.12
  • Fix · CNA Linux (Linux) Fixed in 6.6.160, 6.12.114, 6.18.53, 7.2.7, 7.3

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet: Fix deferred
Red Hat Enterprise Linux 6AffectedNo fix planned: Out of support scope
Red Hat Enterprise Linux 9AffectedNo fix yet: Fix deferred
Red Hat OpenShift Container Platform 4AffectedNo fix yet: Fix deferred
Red Hat OpenShift Container Platform 5AffectedNo fix yet: Fix deferred
Not affected: 4 products
  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Red Hat OpenShift Container Platform 4

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-97975
  2. 2026-10-03 Alias added: GHSA-2vfm-8xc8-7w2c
  3. 2026-10-19 Fix available: Linux/[email protected] · CNA
  4. 2026-10-21 Fix available: Linux/Linux@55b76500546e5f2e7fdd7ae7283530b620de6e61, Linux/[email protected], Linux/[email protected] +1 · CNA
  5. 2026-10-21 2 new references · CNA
  6. 2026-10-23 Affected versions changed · Red Hat
  7. 2026-10-23 CVSS score changed · Red Hat
  8. 2026-11-06 Affected versions changed · Red Hat

References

  • TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
  • TI-2021-02452 Incorrect authorization in Ubuntu linux kernel KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
See all 21741 →

Sources