Use-after-free in Linux kernel Bluetooth SCO sco_recv_frame()
CVE-2026-31408 is a use-after-free vulnerability in the Linux kernel Bluetooth SCO subsystem, specifically in sco_recv_frame(). The function reads conn->sk while holding sco_conn_lock(), but releases the lock without first taking a reference to the socket. If a concurrent close() occurs after the lock is released, the socket can be freed before subsequent access to sk->sk_state, resulting in a dangling pointer dereference and use-after-free condition. The issue is caused by missing reference management for the socket object in a race window between lock release and later socket state access. The upstream fix takes a reference with sco_sock_hold() before releasing the lock and adds sock_put() on all exit paths.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.