CVE-2026-31408 is a use-after-free vulnerability in the Linux kernel Bluetooth SCO (Synchronous Connection-Oriented) subsystem, in net/bluetooth/sco.c. The flaw is in sco_recv_frame(), which reads conn->sk while holding sco_conn_lock() but releases the lock without first retaining a reference to the socket. A concurrent close() can free the socket after the lock is dropped and before subsequent access to sk->sk_state, creating a race that results in use-after-free. The upstream fix takes a socket reference with sco_sock_hold() before releasing the lock and adds sock_put() on all exit paths. The issue is associated with improper reference-count handling and has been reported as present since Linux 2.6.12.
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 SCO use-after-free vulnerability in sco_recv_frame() caused by a missing sock_hold.
Linux kernel Bluetooth SCO use-after-free vulnerability in sco_recv_frame() caused by a missing sock_hold.
A Linux kernel Bluetooth SCO use-after-free vulnerability in sco_recv_frame() caused by a missing sock_hold reference.
A Linux kernel Bluetooth SCO use-after-free vulnerability in sco_recv_frame() caused by a missing sock_hold.
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.