Loading vulnerability…
CVE-2024-41062 is a use-after-free vulnerability caused by missing synchronization between socket release and receive processing in the Linux kernel Bluetooth L2CAP subsystem. The socket-close path can free a socket through l2cap_sock_release(), l2cap_sock_kill(), and sk_free() while hci_rx_work concurrently processes received data through l2cap_sock_recv_cb(). If receive processing accesses the socket after it has been freed, it dereferences an invalid socket pointer. The fix synchronizes the receive callback with socket release using the channel mutex and clears the channel data pointer when the socket is dead.
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.
Socket receive callback and release synchronization issue in Linux kernel Bluetooth L2CAP.
A race condition in the Linux kernel Bluetooth L2CAP subsystem can cause a use-after-free when socket closure frees a socket while hci_rx_work processes incoming data and accesses that socket without synchronization. The fix adds a channel mutex to synchronize the receive callback with socket release and clears the channel data pointer to prevent subsequent access to the freed socket. Affected versions and exploitation impact are not specified.
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.