CVE-2026-64406
Analyzed
Analyzed - Analysis Complete
Use-After-Free in Linux Kernel Bluetooth Stack
Vulnerability report for CVE-2026-64406, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-07-25
Last updated on: 2026-09-04
Assigner: kernel.org
Description
Description
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: fix UAF in bt_accept_dequeue()
bt_accept_get() takes a temporary reference before dropping the accept
queue lock. bt_accept_dequeue() currently drops that reference before
bt_accept_unlink(), leaving only the queue reference.
bt_accept_unlink() drops the queue reference. The subsequent
sock_hold() therefore accesses freed memory if it was the final
reference, as observed by KASAN during listening L2CAP socket cleanup.
Retain the temporary queue-walk reference through unlink and hand it to
the caller on success. Drop it explicitly on the closed and
not-yet-connected paths.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | From 5.15.210 (inc) to 5.15.212 (exc) |
| linux | linux_kernel | 7.2 |
| linux | linux_kernel | 7.2 |
| linux | linux_kernel | From 6.1.175 (inc) to 6.1.178 (exc) |
| linux | linux_kernel | From 6.6.142 (inc) to 6.6.145 (exc) |
| linux | linux_kernel | From 7.0.11 (inc) to 7.1 (exc) |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | From 6.12.92 (inc) to 6.12.96 (exc) |
| linux | linux_kernel | From 6.18.34 (inc) to 6.18.39 (exc) |
| linux | linux_kernel | From 5.10.259 (inc) to 5.10.261 (exc) |
| linux | linux_kernel | From 7.1.1 (inc) to 7.1.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |