Bluetooth: hci_core: Fix UAF in hci_unregister_dev()
CVE-2026-74302 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-74302?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: d6cbce18370641a21dd889e8613d8153df15eb39 to < bce2eec05bce548b548aca52c1834540f97d5d60, 0d151a103775dd9645c78c97f77d6e2a5298d913 to < 48c7ad6afcc58c2cda11fed39791708103b6a644, 0d151a103775dd9645c78c97f77d6e2a5298d913 to < a0fd1086a57b982f8c24ae4ab165c2af39fe1735, 0d151a103775dd9645c78c97f77d6e2a5298d913 to < 672d52d9412252e61b8de8d773ccdf5a277cf540
- Linux Linux: 6.10
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/bce2eec05bce548b548aca52c1834540f97d5d60
- git.kernel.org/stable/c/48c7ad6afcc58c2cda11fed39791708103b6a644
- git.kernel.org/stable/c/a0fd1086a57b982f8c24ae4ab165c2af39fe1735
- git.kernel.org/stable/c/672d52d9412252e61b8de8d773ccdf5a277cf540
- git.kernel.org/stable/c/5edcc018fa6e80b2c478454a4a8229c23d67c181
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON