Bluetooth: hci_conn: fix potential UAF in create_big_sync
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.183, 6.6.140, 6.12.90, 6.18.32, 7.0.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From eca0ae4aea66914515e5e3098ea051b518ee5316 · fixed in d41093723e47255d7d74df86e2736711c1b8486e; From eca0ae4aea66914515e5e3098ea051b518ee5316 · fixed in 6823f730bf195fc296d9edd09e2ca94bc1ff5584; From eca0ae4aea66914515e5e3098ea051b518ee5316 · fixed in 1750a2df0eab61dc421a7afae74abdd239a44b85; From eca0ae4aea66914515e5e3098ea051b518ee5316 · fixed in dc34f8d8240f25dd137dc2758ebbcc75e3779142; From eca0ae4aea66914515e5e3098ea051b518ee5316 · fixed in f8eaf92c57ad99358dd372580d5ff87623343a72; From eca0ae4aea66914515e5e3098ea051b518ee5316 · fixed in 0beddb0c380bed5f5b8e61ddbe14635bb73d0b41
- Linux Linux
6.0
- KernelLinux
From 6.0.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.90; From 6.13.0 · fixed in 6.18.32; From 6.19.0 · fixed in 7.0.7