Loading vulnerability…
A use-after-free vulnerability existed in the Linux kernel Bluetooth subsystem in the hci_event handling path, specifically in hci_conn_tx_dequeue while processing HCI_EV_NUM_COMP_PKTS. The flaw was caused by improper locking of the HCI device object during event processing, allowing an HCI connection object to be freed concurrently and then accessed by Bluetooth workqueue processing. Diagnostic traces showed the stale object being allocated during Bluetooth LE connection completion handling and later freed through connection teardown paths before being dereferenced in hci_conn_tx_dequeue. This is a kernel memory-safety flaw in net/bluetooth/hci_conn.c that can lead to invalid memory access during receipt and handling of Bluetooth controller events.
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 use-after-free vulnerability in hci_conn_tx_dequeue.
A Linux kernel Bluetooth use-after-free vulnerability in hci_conn_tx_dequeue.
A Linux kernel Bluetooth vulnerability involving a use-after-free in hci_conn_tx_dequeue.
A Linux kernel Bluetooth use-after-free vulnerability in hci_event during hci_conn_tx_dequeue processing.
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.