CVE-2026-80762
Bluetooth: hci_sync: Fix accept list UAF during suspend
Reported by linux · Published September 4, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix accept list UAF during suspend hci_update_event_filter_sync() walks hdev->accept_list while sending a synchronous HCI command for each remote-wakeup device. The suspend path holds hdev->req_lock, but accept-list updates are serialized by hdev->lock. Consequently, remove_device() can free the current list entry during the controller wait. The following interleaving causes the use-after-free: hci_update_event_filter_sync() remove_device() fetch accept-list entry hci_set_event_filter_sync() wait for controller response hci_dev_lock() list_del() kfree() hci_dev_unlock() read the freed list.next KASAN reported: BUG: KASAN: slab-use-after-free in hci_suspend_sync+0x835/0x910 Read of size 8 at addr ffff88810bec8440 by task kworker/0:1/10 Workqueue: events vhci_suspend_work Call Trace: hci_suspend_sync+0x835/0x910 hci_suspend_dev+0x182/0x450 process_one_work+0x661/0x1090 worker_thread+0x45b/0xd10 Allocated by task 86: hci_bdaddr_list_add_with_flags+0x1a8/0x400 add_device+0x381/0x820 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 91: kfree+0x131/0x3c0 remove_device+0x429/0xb70 hci_sock_sendmsg+0x1033/0x1ea0 Snapshot the remote-wakeup addresses under hdev->lock. Release the lock before sending HCI commands. Clear the controller event filter before building the snapshot, and skip allocation and the second list traversal when there are no matching entries. This preserves the original filter and scan-state updates without retaining an accept-list node across a controller wait.
EPSS 0.17% · 6.7th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | fe93a697a7a92fa9adf78c9ff67a10db3193290c, f57b399c4fa1501b2d5451f52d861ece86bcf3db, bb5f5414d1a6272a16f68684e998f4063dd19f57, b5181516a9f5c2fdb3271cdad72a5b16c6963a44, 95bb57bc11a91caf042ad00fca85e480d3fda37f, 87ad116ac3abc6f2ce2b5b6c488f633003581eee, 29c59212a507804d7616b8abf491d30b4ab8e75f |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 182ee45da083db4e3e621541ccf255bfa9652214, 182ee45da083db4e3e621541ccf255bfa9652214, 182ee45da083db4e3e621541ccf255bfa9652214 |
| Linux | Linux | 5.17, 0, 6.1.187 |
| Linux | Linux | 7.3, 0, 6.1.187 |
| linux | linux_kernel | 5.17, 5.17, 5.17 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (11 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80762
vulnetix vdb fixes CVE-2026-80762
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80762/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart