Loading vulnerability…
CVE-2026-31408 is a use-after-free vulnerability in the Linux kernel Bluetooth SCO subsystem, in sco_recv_frame(). The function reads conn->sk while holding sco_conn_lock() but releases the lock without retaining a socket reference. A concurrent close() can then free the socket before sco_recv_frame() accesses sk->sk_state. The flaw was introduced in Linux 2.6.12. The upstream correction obtains the socket reference with sco_sock_hold() before releasing the lock and releases it with sock_put() on all exit paths.
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.
25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by the referenced CentOS Stream 8 TuxCare security update; no technical details are provided.
A vulnerability addressed by the referenced CentOS 7 security advisory; no technical flaw details are provided.
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.
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.