CVE 7.8 HIGH

Bluetooth: hci_conn: fix potential UAF in create_big_sync_CVE-2026-46111

7.8 / 10
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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().

Basic Information

ID CVE-2026-46111
Source Linux
Published May 28, 2026 at 09:35
Modified May 30, 2026 at 10:47

Affected Product

Vendor Linux
Product Linux
Version eca0ae4aea66914515e5e3098ea051b518ee5316
Affected Versions Linux Linux eca0ae4aea66914515e5e3098ea051b518ee5316
Linux Linux eca0ae4aea66914515e5e3098ea051b518ee5316
Linux Linux eca0ae4aea66914515e5e3098ea051b518ee5316
Linux Linux eca0ae4aea66914515e5e3098ea051b518ee5316
Linux Linux eca0ae4aea66914515e5e3098ea051b518ee5316
Linux Linux 6.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.