Loading vulnerability…
CVE-2025-40301 is an uninitialized-memory read in the Linux kernel Bluetooth HCI command-complete event handler. When hci_cmd_complete_evt() receives a command-complete event for an unknown opcode, it assumes a remaining buffer byte contains the return status. Prior parameter processing can consume all remaining data, leaving the socket buffer empty. The subsequent return-status read then accesses uninitialized memory. The fix validates the socket-buffer length before accessing the return-status byte.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel Bluetooth HCI event-handling flaw in which processing a command-complete event with an unknown opcode could read uninitialized memory when the socket buffer has no remaining data. The resolved fix validates skb length before reading the return-status byte.
A Linux kernel vulnerability in Bluetooth HCI event handling that can cause information disclosure and denial of service.
A Linux kernel Bluetooth HCI event handling vulnerability that can cause information disclosure and denial of service.
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.