CVE-2026-46111

Bluetooth: hci_conn: fix potential UAF in create_big_sync

HIGH
7.8
CVSS Score
Published: May 28, 2026 at 09:35 AM UTC
Updated: October 19, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fix potential UAF in create_big_sync Add hci_conn_valid() check in create_big_sync() to detect stale connections before proceeding with BIG creation. Handle the resulting -ECANCELED in create_big_complete() and re-validate the connection under hci_dev_lock() before dereferencing, matching the pattern used by create_le_conn_complete() and create_pa_complete(). Keep the hci_conn object alive across the async boundary by taking a reference via hci_conn_get() when queueing create_big_sync(), and dropping it in the completion callback. The refcount and the lock are complementary: the refcount keeps the object allocated, while hci_dev_lock() serializes hci_conn_hash_del()'s list_del_rcu() on hdev->conn_hash, as required by hci_conn_del(). hci_conn_put() is called outside hci_dev_unlock() so the final put (which resolves to kfree() via bt_link_release) does not run under hdev->lock, though the release path would be safe either way. Without this, create_big_complete() would unconditionally dereference the conn pointer on error, causing a use-after-free via hci_connect_cfm() and hci_conn_del().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.6.1406.13 ≤ v < 6.18.326.19 ≤ v < 7.0.76.7 ≤ v < 6.12.907.17.1 rc17.1 rc2eca0ae4aea66914515e5e3098ea051b518ee5316
Vendor states this is fixed in 0beddb0c380bed5f5b8e61ddbe14635bb73d0b41 (fixed)
Vendor states this is fixed in 1750a2df0eab61dc421a7afae74abdd239a44b85 (fixed)
Vendor states this is fixed in 6823f730bf195fc296d9edd09e2ca94bc1ff5584 (fixed)
Vendor states this is fixed in d41093723e47255d7d74df86e2736711c1b8486e (fixed)
Vendor states this is fixed in dc34f8d8240f25dd137dc2758ebbcc75e3779142 (fixed)
Vendor states this is fixed in f8eaf92c57ad99358dd372580d5ff87623343a72 (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.90 (unaffected)
Vendor states this is fixed in 6.18.32 (unaffected)
Vendor states this is fixed in 6.6.140 (unaffected)
Vendor states this is fixed in 7.0.7 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusUNDERGOING ANALYSIS
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card