CVE-2025-40318 is a race condition in the Linux kernel Bluetooth hci_sync subsystem. The hci_cmd_sync_dequeue_once() function performed lookup and cancellation of a command-synchronization entry under separate cmd_sync_work_lock critical sections. During the interval between these operations, hci_cmd_sync_work() could remove the same entry. The resulting concurrent deletion could invoke list removal twice and cause a use-after-free. The upstream fix retains cmd_sync_work_lock across both lookup and cancellation, preventing concurrent removal of the entry.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel Bluetooth vulnerability involving a race condition in hci_cmd_sync_dequeue_once.
A Linux kernel Bluetooth vulnerability involving a race in hci_cmd_sync_dequeue_once.
A Linux kernel Bluetooth hci_sync race condition vulnerability in hci_cmd_sync_dequeue_once.
A Linux kernel Bluetooth hci_sync race condition causing a use-after-free due to concurrent deletion of the same entry in hci_cmd_sync_dequeue_once() and hci_cmd_sync_work().
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.