CVE-2026-80764: Bluetooth: hci_event: fix LE list UAF on reset
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 0628cc9b2fa29985a7b8c774741f8a736b0f5e7c, 25b05e3ce31d954540e99954bcc66cbceb27ab35, 3.19; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 0628cc9b2fa29985a7b8c774741f8a736b0f5e7c, 25b05e3ce31d954540e99954bcc66cbceb27ab35, 3.19; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 0de8cd646b0152c9ddd10257d8284938d0df0181, 3.19affected
- a4d5504d5c39cc84f1f828e19967595597a8136e and later · before 8e68c380290b1dd64a0a512ce66d0264130c46edaffected · git
- a4d5504d5c39cc84f1f828e19967595597a8136e and later · before 0628cc9b2fa29985a7b8c774741f8a736b0f5e7caffected · git
- a4d5504d5c39cc84f1f828e19967595597a8136e and later · before d57702d4c55633c243da5a2fec37ae2ad4adb621affected · git
- a4d5504d5c39cc84f1f828e19967595597a8136e and later · before 39a3afb91be3cb465f46ce7a8e5696d9e33edf93affected · git
- a4d5504d5c39cc84f1f828e19967595597a8136e and later · before b55e83a4ba31d40deae22d4e4dc8c84083e953c6affected · git
- a4d5504d5c39cc84f1f828e19967595597a8136e and later · before 25b05e3ce31d954540e99954bcc66cbceb27ab35affected · git
- a4d5504d5c39cc84f1f828e19967595597a8136e and later · before 33af47e847fe4a28b109673affb5874015d54f5aaffected · git
- 3.18.3 and later · before 3.19affected · semver
- before 3.19not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.5-1.1 | 7.2.5-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80762Sep 4, 2026 · Bluetooth: hci_sync: Fix accept list UAF during suspend0Monitor
- ← EarlierCVE-2026-80763Sep 4, 2026 · Bluetooth: hci_event: validate LE Set CIG Parameters response0Monitor
- Later →CVE-2026-80765Sep 4, 2026 · HID: hyperv: validate initial device info bounds0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0628cc9b2fa29985a7b8c774741f8a736b0f5e7c | Vendor (CNA) |
| Linux Linux | 25b05e3ce31d954540e99954bcc66cbceb27ab35 | Vendor (CNA) |
| Linux Linux | 3.19 | Vendor (CNA) |
| Linux Linux | 33af47e847fe4a28b109673affb5874015d54f5a | Vendor (CNA) |
| Linux Linux | 39a3afb91be3cb465f46ce7a8e5696d9e33edf93 | Vendor (CNA) |
| Linux Linux | 8e68c380290b1dd64a0a512ce66d0264130c46ed | Vendor (CNA) |
| Linux Linux | b55e83a4ba31d40deae22d4e4dc8c84083e953c6 | Vendor (CNA) |
| Linux Linux | d57702d4c55633c243da5a2fec37ae2ad4adb621 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/25b05e3ce31d954540e99954bcc66cbceb27ab35
- git.kernel.org/stable/c/33af47e847fe4a28b109673affb5874015d54f5a
- git.kernel.org/stable/c/39a3afb91be3cb465f46ce7a8e5696d9e33edf93
- git.kernel.org/stable/c/8e68c380290b1dd64a0a512ce66d0264130c46ed
- git.kernel.org/stable/c/b55e83a4ba31d40deae22d4e4dc8c84083e953c6
- git.kernel.org/stable/c/d57702d4c55633c243da5a2fec37ae2ad4adb621
Vendor advisories and official records. Exploit/PoC links are deliberately left out.