CVE-2026-80764

CVE CVE-2026-80764EUVD EUVD-2026-71407Published 2026-09-04T15:12:36.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: fix LE list UAF on reset hci_cc_reset() clears the LE accept and resolving lists without taking hdev->lock. Other command-complete handlers serialize updates to these lists with that lock, and the debugfs readers hold it while walking them. This permits the reset completion and a debugfs read to interleave as follows: hci_rx_work debugfs reader ----------- -------------- lock hdev->lock fetch current entry list_del(entry) kfree(entry) read entry fields The reader then dereferences a freed list entry and may follow its stale next pointer. KASAN reported: BUG: KASAN: slab-use-after-free in white_list_show+0x15f/0x180 Read of size 1 at addr ffff8881015dab16 by task poc/95 Call Trace: white_list_show+0x15f/0x180 seq_read_iter+0x3ff/0x1190 seq_read+0x267/0x3d0 vfs_read+0x177/0xa20 ksys_read+0xf7/0x1c0 Allocated by task 91: hci_bdaddr_list_add+0x1a6/0x3a0 hci_cc_le_add_to_accept_list+0xab/0x140 hci_cmd_complete_evt+0x26c/0x9a0 hci_event_packet+0x454/0xb20 hci_rx_work+0x293/0x730 Freed by task 90: kfree+0x131/0x3c0 hci_bdaddr_list_clear+0xd8/0x160 hci_cc_reset+0x28a/0x370 hci_cmd_complete_evt+0x26c/0x9a0 hci_event_packet+0x454/0xb20 hci_rx_work+0x293/0x730 Take hdev->lock around both list clears. This matches the existing mutation and traversal locking convention.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.1.185; a4d5504d5c39cc84f1f828e19967595597a8136e <b55e83a4ba31d40deae22d4e4dc8c84083e953c6; patch: 7.1.11; a4d5504d5c39cc84f1f828e19967595597a8136e <8e68c380290b1dd64a0a512ce66d0264130c46ed; a4d5504d5c39cc84f1f828e19967595597a8136e <39a3afb91be3cb465f46ce7a8e5696d9e33edf93; a4d5504d5c39cc84f1f828e19967595597a8136e <33af47e847fe4a28b109673affb5874015d54f5a; patch: 6.18.47; patch: 6.12.106; a4d5504d5c39cc84f1f828e19967595597a8136e <0628cc9b2fa29985a7b8c774741f8a736b0f5e7c; patch: 0; 3.18.3 <3.19; patch: 7.3-rc1; 3.19; a4d5504d5c39cc84f1f828e19967595597a8136e <25b05e3ce31d954540e99954bcc66cbceb27ab35; a4d5504d5c39cc84f1f828e19967595597a8136e <d57702d4c55633c243da5a2fec37ae2ad4adb621; patch: 6.6.154; 0de8cd646b0152c9ddd10257d8284938d0df0181; patch: 7.2.1

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.