A use-after-free flaw in the Linux kernel Bluetooth L2CAP receive path arises from a race between SDU reassembly and socket receive processing. l2cap_reassemble_sdu() can queue an SKB to a socket, after which a concurrent bt_sock_recvmsg() invocation can dequeue and free that SKB. Subsequent L2CAP receive-state processing may continue to access struct l2cap_ctrl held in the freed SKB control buffer, resulting in a use-after-free read in l2cap_rx_state_recv. The fix preserves a local copy of the L2CAP control structure rather than accessing it after reassembly returns.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CVE listed in the advisory references, but the provided content does not describe the underlying vulnerability.
A CVE referenced by the Red Hat Enterprise Linux 7 kernel security advisory; the supplied content does not describe the flaw.
Unknown; the advisory lists this CVE but provides no vulnerability description.
An important Linux kernel Bluetooth L2CAP use-after-free vulnerability (CWE-416). It results from a race condition involving l2cap_reassemble_sdu and socket receive processing while Bluetooth is in use, with potential confidentiality, integrity, and availability impact. Red Hat assigns CVSS 7.1 for its products.
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.