CVE-2026-74302

Bluetooth: hci_core: Fix UAF in hci_unregister_dev()

HIGH

7.8

CVSS Score

Published: August 15, 2026 at 05:58 AM UTC

Updated: October 21, 2026 at 01:19 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.1%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() hci_unregister_dev() does not disable cmd_timer and ncmd_timer before the hci_dev structure is freed. If a timeout fires during device teardown, the callback dereferences freed memory (including the hdev->reset function pointer), leading to a use-after-free. Add disable_delayed_work_sync() calls alongside the existing disable_work_sync() calls to ensure both timers are fully quiesced before teardown proceeds.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

90%

0d151a103775dd9645c78c97f77d6e2a5298d9133f939bd73fed12dddc2a32a76116c19ca47c76784.19.31948542881997e17b49dc16b93fe910e0cfcf7a9f95.10.223 5.15.164 5.4.281 6.1.101 6.10 6.6.42 6.9.1196600c2e5ee8213dbab5df1617293d8e847bb4fa9cfc84b1d464cc024286f42a090718f9067b80edd2ce562a5aff1dcd0c50d9808ea825ef90da909fd6cbce18370641a21dd889e8613d8153df15eb39ddeda6ca5f218b668b560d90fc31ae469adbfd92

Vendor states this is fixed in 48c7ad6afcc58c2cda11fed39791708103b6a644 (fixed)

Vendor states this is fixed in 5edcc018fa6e80b2c478454a4a8229c23d67c181 (fixed)

Vendor states this is fixed in 672d52d9412252e61b8de8d773ccdf5a277cf540 (fixed)

Vendor states this is fixed in a0fd1086a57b982f8c24ae4ab165c2af39fe1735 (fixed)

Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.10 (unaffected)

Vendor states this is fixed in 6.12.97 (unaffected)

Vendor states this is fixed in 6.18.40 (unaffected)

Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.6.160 (unaffected)

Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 7.1.5 (unaffected)

Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (5)

Source: cverecord

https://git.kernel.org/stable/c/48c7ad6afcc58c2cda11fed39791708103b6a644

Source: cverecord

https://git.kernel.org/stable/c/a0fd1086a57b982f8c24ae4ab165c2af39fe1735

Source: cverecord

https://git.kernel.org/stable/c/672d52d9412252e61b8de8d773ccdf5a277cf540

Source: cverecord

https://git.kernel.org/stable/c/5edcc018fa6e80b2c478454a4a8229c23d67c181

Source: cverecord

https://git.kernel.org/stable/c/bce2eec05bce548b548aca52c1834540f97d5d60

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux

Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card