Loading vulnerability…
CVE-2025-38250 is a race-condition use-after-free in the Linux kernel Bluetooth HCI core virtual HCI (VHCI) driver. Concurrent close() and ioctl-triggered device-reset operations can cause vhci_release() to unregister the HCI device and free its associated VHCI data while an in-flight hci_dev_reset() reaches vhci_flush() and accesses that freed data. The race exists because hci_unregister_dev() unlinks the device without synchronizing against operations that obtained the device before unlinking. The upstream fix executes hci_dev_reset() under SRCU protection and waits for in-flight reset operations to complete during device unregistration.
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.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel Bluetooth HCI core use-after-free vulnerability in vhci_flush().
A use-after-free vulnerability in the Linux kernel Bluetooth hci_core component's vhci_flush() function.
A use-after-free vulnerability in the Linux kernel Bluetooth hci_core vhci_flush() function.
Use-after-free vulnerability in the Linux kernel Bluetooth hci_core vhci_flush() function.
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.