data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-74528 in the interactive tracker

CVE-2026-74528

Bluetooth: hci_sync: hold conn in hci_past_sync() callback

8.0 EPSS 0.4% AV:A

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-74528 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

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixienot affected6.12.113-1Nothing to do. trixie never shipped the vulnerable code.
Debian 14forkyfixed7.1.8-1Update the kernel and reboot. Fixed in 7.1.8-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.8-1Update 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

Avoids giving freed pointers to hci_conn_valid(), which kmalloc may have reused. Hold refcount to avoid that.

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 bluetooth

Prints 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.0 high
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it
Attack vector
adjacent network (AV:A)source
EPSS
0.36%, higher than 28.1% 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

IntroducedFixed inCommit
6.197.1.8e6792adef614
6.197.2abf9753edf3f

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 PAST handling reached via ISO socket bind() rebind; exploitation requires an active LE connection to an adjacent peer and the freeing race is routinely won by concurrent local disconnects or a remote BLE link teardown, matching the CNA Bluetooth-adjacent threat model for phones and laptops in radio range.
AC:LAttack complexity, low
An attacker controls both sides of the race by calling bind() to queue hci_past_sync() while concurrently closing the ISO socket or tearing down the looked-up LE link; repeated attempts can reliably free hci_conn objects before the hci_cmd_sync work callback runs without uncontrollable layout or timing dependencies.
PR:LPrivileges required, low
Once the ISO socket layer is active (typically enabled by bluetoothd at boot), any unprivileged local user can open AF_BLUETOOTH SOCK_SEQPACKET ISO sockets and invoke the vulnerable bind() rebind path without CAP_NET_ADMIN; Bluetooth sockets are restricted to init_net and are not available through user namespaces.
UI:NUser interaction, none
Exploitation is driven entirely by the attacker's own socket operations and coordinated disconnects; no action by another user or administrator (pairing prompts, mounting, or opening files) is required beyond normal Bluetooth being enabled on the host.
S:UScope, unchanged
The use-after-free corrupts kernel heap objects and enables standard local kernel privilege escalation within the same security authority; it does not cross VM, hypervisor, or IOMMU boundaries.
C:HConfidentiality impact, high
Without refcounting, freed hci_conn pointers are passed to hci_conn_valid(); if kmalloc reuses the slab for another hci_conn the check can succeed and the callback reads handle, sync_handle, and iso_qos fields from attacker-influenced freed/reused memory, giving UAF-based kernel information disclosure.
I:HIntegrity impact, high
Slab reuse of the freed hci_conn lets an attacker shape heap contents so stale pointer dereferences and subsequent HCI PAST commands operate on attacker-controlled data, providing the memory corruption and arbitrary-write primitives typical of kernel use-after-free exploitation.
A:HAvailability impact, high
Use-after-free on hci_conn structures in hci_cmd_sync work can cause KASAN slab-use-after-free reports, kernel oopses, or panics when freed memory is reused or corrupted, and misdirected PAST HCI commands can additionally disrupt or wedge Bluetooth connectivity on the host.