GHSA-8PVH-G785-QF97
Vulnerability from github – Published: 2026-09-04 18:31 – Updated: 2026-09-04 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-80764"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-04T16:18:01Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: fix LE list UAF on reset\n\nhci_cc_reset() clears the LE accept and resolving lists without taking\nhdev-\u003elock. Other command-complete handlers serialize updates to these\nlists with that lock, and the debugfs readers hold it while walking them.\n\nThis permits the reset completion and a debugfs read to interleave as\nfollows:\n\n hci_rx_work debugfs reader\n ----------- --------------\n lock hdev-\u003elock\n fetch current entry\n list_del(entry)\n kfree(entry)\n read entry fields\n\nThe reader then dereferences a freed list entry and may follow its stale\nnext pointer.\n\nKASAN reported:\n\n BUG: KASAN: slab-use-after-free in white_list_show+0x15f/0x180\n Read of size 1 at addr ffff8881015dab16 by task poc/95\n\n Call Trace:\n white_list_show+0x15f/0x180\n seq_read_iter+0x3ff/0x1190\n seq_read+0x267/0x3d0\n vfs_read+0x177/0xa20\n ksys_read+0xf7/0x1c0\n\n Allocated by task 91:\n hci_bdaddr_list_add+0x1a6/0x3a0\n hci_cc_le_add_to_accept_list+0xab/0x140\n hci_cmd_complete_evt+0x26c/0x9a0\n hci_event_packet+0x454/0xb20\n hci_rx_work+0x293/0x730\n\n Freed by task 90:\n kfree+0x131/0x3c0\n hci_bdaddr_list_clear+0xd8/0x160\n hci_cc_reset+0x28a/0x370\n hci_cmd_complete_evt+0x26c/0x9a0\n hci_event_packet+0x454/0xb20\n hci_rx_work+0x293/0x730\n\nTake hdev-\u003elock around both list clears. This matches the existing\nmutation and traversal locking convention.",
"id": "GHSA-8pvh-g785-qf97",
"modified": "2026-09-04T18:31:24Z",
"published": "2026-09-04T18:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80764"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0628cc9b2fa29985a7b8c774741f8a736b0f5e7c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/25b05e3ce31d954540e99954bcc66cbceb27ab35"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/33af47e847fe4a28b109673affb5874015d54f5a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/39a3afb91be3cb465f46ce7a8e5696d9e33edf93"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8e68c380290b1dd64a0a512ce66d0264130c46ed"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b55e83a4ba31d40deae22d4e4dc8c84083e953c6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d57702d4c55633c243da5a2fec37ae2ad4adb621"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.