Loading vulnerability…
CVE-2025-40258 is a use-after-free vulnerability in the Linux kernel Multipath TCP (MPTCP) subsystem's mptcp_schedule_work() function. The affected logic queued work with schedule_work() before acquiring a reference to the associated socket with sock_hold(). The MPTCP worker could execute immediately, release the final socket reference, and free the socket before the scheduling thread attempted its reference increment. This results in a refcount operation on a freed socket object. The fix acquires the socket reference before queuing work and drops that reference if work scheduling fails.
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.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel MPTCP race condition vulnerability in mptcp_schedule_work().
A Linux kernel MPTCP race condition vulnerability in mptcp_schedule_work().
A Linux kernel MPTCP race condition vulnerability in mptcp_schedule_work().
A Linux kernel MPTCP race condition vulnerability in mptcp_schedule_work().
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.