Look up another CVE · open CVE-2026-74530 in the interactive tracker
CVE-2026-74530
Bluetooth: hci_sync: hold conn in hci_connect_big_sync() callback
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem net/bluetooth. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-74530 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.1.8-1 | Update the kernel and reboot. Fixed in 7.1.8-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.8-1 | Update the kernel and reboot. Fixed in 7.1.8-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
There is theoretical UAF if the conn is freed while the hci_sync task is running. Hold refcount to avoid that. Handle NULL hcon, return 0 + do nothing to match the previous behavior.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
net/bluetooth/hci_sync.c
- What this is
- BLUETOOTH SUBSYSTEMMAINTAINERS section matched on net/bluetooth/ · linux-bluetooth@vger.kernel.org · Supported
- Kernel module
- bluetooth
Check it on the machine
grep -w CONFIG_BT /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w bluetoothPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_BT
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.38%, higher than 29.9% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- net/bluetooth
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.15 | 6.18.57 | ff5625d27415 |
| 6.15 | 7.1.8 | 2d91e6244b69 |
| 6.15 | 7.2 | 56e78b670356 |
| 6.12.28 | 0 | 0 |
| 6.14.6 | 0 | 0 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:AAttack vector, adjacent network
- The bug is in Bluetooth LE ISO BIG Create Sync handling (hci_connect_big_sync), reachable via adjacent BLE traffic that drives HCI events (e.g. HCI_EVT_LE_BIG_INFO_ADV_REPORT through iso_connect_ind) and via local ISO sockets; Bluetooth kernel bugs are scored as Adjacent, not Network.
- AC:LAttack complexity, low
- After 024421cf3992 the path blocks in __hci_cmd_sync_status_sk for up to conn_timeout while only holding a bare hci_conn pointer; an attacker who can open/close an ISO broadcast socket (or race teardown during that wait) controls both sides of the race and can reliably trigger the UAF.
- PR:NPrivileges required, none
- Exploitation does not require root or CAP_NET_ADMIN; adjacent attackers can trigger the vulnerable code through unauthenticated over-the-air BLE broadcasts processed by the kernel HCI layer, and local exploitation only needs standard Bluetooth/ISO socket access available to unprivileged users/apps with Bluetooth permission.
- UI:NUser interaction, none
- No victim interaction is required beyond attacker-controlled actions such as creating an ISO broadcast listener socket, starting BIG sync, and concurrently closing the socket to free hci_conn while hci_sync work is still running; exploitation does not depend on another user opening files or mounting resources.
- S:UScope, unchanged
- The use-after-free corrupts kernel heap memory within the Bluetooth/hci_conn subsystem and can lead to local privilege escalation, but it does not cross a VM, IOMMU, or sandbox security boundary into another authority domain.
- C:HConfidentiality impact, high
- This is a kernel heap use-after-free of struct hci_conn; freed connection objects can be reallocated and read through subsequent dereferences in create_big_complete and hci_le_big_create_sync, providing a standard path to arbitrary kernel memory disclosure.
- I:HIntegrity impact, high
- UAF on struct hci_conn allows corrupting connection flags and adjacent heap contents; the structure contains function pointers (cleanup, connect_cfm_cb, disconn_cfm_cb) and is large enough to support heap grooming toward arbitrary write or control-flow hijack.
- A:HAvailability impact, high
- Use-after-free during clear_bit on conn->flags in create_big_complete, or accessing conn fields after teardown during the blocking BIG sync command, can cause kernel oops/panic and repeated disruption; UAF availability impact is rated High per kernel guidance.