Answer in brief
CVE-2025-40318 records a High severity (CVSS 8.8) vulnerability in Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f00f36db76eb8fd10d13e80e2590f23b5beaa54d <0a94f7e017438935c09ef833a1aa908ad9875213 || >=1499f79995c7ee58e3bfeeff75f6d1b37dcda881 <932c0a4f77ac13e526fdd5b42914d29c9821d389 || >=505ea2b295929e7be2b4e1bc86ee31cb7862fb01 <ae76cf6c2c842944c6514c57df54d728f1916553 || >=505ea2b295929e7be2b4e1bc86ee31cb7862fb01 <9cd536970192b72257afcdfba0bfc09993e6f19c || >=505ea2b295929e7be2b4e1bc86ee31cb7862fb01 <09b0cd1297b4dbfe736aeaa0ceeab2265f47f772 || 357603f4d396d85fbf0045512efaf1d7f7394ed7 || >=6.1.120 <6.1.159 || >=6.6.51 <6.6.117 || >=6.8.9 <6.9 | 0a94f7e017438935c09ef833a1aa908ad9875213, 932c0a4f77ac13e526fdd5b42914d29c9821d389, ae76cf6c2c842944c6514c57df54d728f1916553, 9cd536970192b72257afcdfba0bfc09993e6f19c, 09b0cd1297b4dbfe736aeaa0ceeab2265f47f772, 6.1.159, 6.6.117, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Dec 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once hci_cmd_sync_dequeue_once() does lookup and then cancel the entry under two separate lock sections. Meanwhile, hci_cmd_sync_work() can also delete the same entry, leading to double list_del() and "UAF". Fix this by holding cmd_sync_work_lock across both lookup and cancel, so that the entry cannot be removed concurrently.
Quoted source text, attributed separately from HOL analysis.