Loading vulnerability…
CVE-2026-64206 is a locking flaw in the Linux kernel Bluetooth L2CAP subsystem. The issue occurs during connection teardown in l2cap_conn_del(), which acquired conn->lock and then called cancel_work_sync() on pending_rx_work. The pending receive worker, process_pending_rx(), also acquires the same mutex. This creates a circular locking condition in which teardown waits for the worker to finish while the worker waits for the mutex already held by teardown, resulting in a deadlock. The fix changes the ordering so pending_rx_work is cancelled before conn->lock is taken, while preserving later queue cleanup after the lock is acquired.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.