HIGH Introduced in 6.1
bluetooth SyncSetup UAF
CVE-2026-90255
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.5HIGH
01Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fix the SCO setup context lifetime hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry->data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered. The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry->data == conn and entry->data is the wrapper here. Same problem as commit 2f5d635ad590 ("Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks"). Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the destroy callback when it fails to queue.
02KernelScan AI Analysis
Risk summary
A use-after-free exists in the Bluetooth SCO connection setup path where asynchronous work holds an unreferenced pointer to a connection that can be freed before the work runs. A nearby Bluetooth device or a local unprivileged process can trigger connection setup and rapid teardown to exploit the race, leading to kernel memory corruption or a crash.
Vulnerability analysis
When setting up a Bluetooth SCO audio link, the kernel queues asynchronous work carrying a pointer to the connection object without holding a reference count on it. If the connection is torn down before that queued work executes—either by the remote Bluetooth device disconnecting or by a local process closing the link—the work accesses memory that has already been freed, resulting in a use-after-free. A secondary issue is that the work context itself is leaked whenever the setup is cancelled rather than completed, because no cleanup callback was registered. The fix takes a reference on the connection before queuing the work and installs a destroy callback that releases both the connection reference and the work context, ensuring neither outlives the other. The submission failure path also drops both references explicitly since the destroy callback is not invoked when queueing fails. This is reachable by any Bluetooth device in wireless range that can initiate and tear down SCO connections, or by a local process with access to Bluetooth sockets; no special privileges are required.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.1 | 6.1 | 6.1.188 | 37cfec41365c |
| 6.12 | 6.1 | 6.12.110 | a661de0ee29d |
| 6.18 | 6.1 | 6.18.52 | c1fe3c74a89a |
| 6.6 | 6.1 | 6.6.157 | 9a2ba69cebe3 |
| 7.2 | 6.1 | 7.2.6 | 4d7b1c834d27 |
| mainline | 6.1 | 7.3 | 42de40abe25d |
| cip/6.1 | 6.1 | 6.1.189-cip61 | 37cfec41365c |
| cip/6.1-rt | 6.1 | 6.1.189-cip61-rt32 | 37cfec41365c |
| cip/6.12 | 6.1 | 6.12.111-cip32 | a661de0ee29d |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.111-cip32 |
| cip/6.1 | Fixed in 6.1.189-cip61 |
| cip/6.1-rt | Fixed in 6.1.189-cip61-rt32 |