Bluetooth: hci_conn: fix the SCO setup context lifetime
Summary
| CVE | CVE-2026-90255 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-17 17:17:21 UTC |
|---|
| Updated | 2026-09-17 17:17:21 UTC |
|---|
| Description | 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected e07a06b4eb417f5271d33ce2240e93c62d98b7b4 37cfec41365c826d5496ef5d00c9e215eee53aa2 git |
Not specified |
| CNA |
Linux |
Linux |
affected e07a06b4eb417f5271d33ce2240e93c62d98b7b4 9a2ba69cebe3fc5a3d4fa8eaaad3c42862723c27 git |
Not specified |
| CNA |
Linux |
Linux |
affected e07a06b4eb417f5271d33ce2240e93c62d98b7b4 a661de0ee29d0915c5e924edf91d2be2b4d35bae git |
Not specified |
| CNA |
Linux |
Linux |
affected e07a06b4eb417f5271d33ce2240e93c62d98b7b4 c1fe3c74a89a7749cba3caa0dd91236049c66116 git |
Not specified |
| CNA |
Linux |
Linux |
affected e07a06b4eb417f5271d33ce2240e93c62d98b7b4 4d7b1c834d2775b73c65e4888e01f5af8b477fe9 git |
Not specified |
| CNA |
Linux |
Linux |
affected e07a06b4eb417f5271d33ce2240e93c62d98b7b4 42de40abe25db9211107af8896d0fd741f10648d git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.1 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/42de40abe25db9211107af8896d0fd741f10648d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4d7b1c834d2775b73c65e4888e01f5af8b477fe9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c1fe3c74a89a7749cba3caa0dd91236049c66116 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/37cfec41365c826d5496ef5d00c9e215eee53aa2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9a2ba69cebe3fc5a3d4fa8eaaad3c42862723c27 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a661de0ee29d0915c5e924edf91d2be2b4d35bae |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.