Loading vulnerability…
CVE-2025-39981 is a memory-safety vulnerability in the Linux kernel Bluetooth management subsystem affecting mgmt_pending lifecycle handling in the MGMT code paths. The flaw arises because a struct mgmt_pending object can be freed while it is still being processed, or can remain reachable from the pending command list after completion handling, creating a stale reference condition. Reported crash data shows a slab use-after-free in mgmt_add_adv_patterns_monitor_sync, with allocation through mgmt_pending_new and mgmt_pending_add and freeing through mgmt_pending_free during pending-list traversal in power-off and device-close paths. The upstream fix adds validation to confirm that a pending object is still present on the pending list and removes commands from that list while holding the associated lock to prevent TOCTOU races. The issue was introduced in Linux kernel 5.17 and fixed upstream in 6.16.10 and 6.17.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel Bluetooth MGMT use-after-free vulnerability.
A Linux kernel Bluetooth MGMT use-after-free vulnerability.
A Linux kernel Bluetooth MGMT use-after-free vulnerability.
A Linux kernel Bluetooth MGMT use-after-free vulnerability.
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.