Loading vulnerability…
CVE-2025-23142 is a use-after-free vulnerability in the Linux kernel SCTP sendmsg path. SCTP can reuse an association and transport selected from the socket endpoint and destination address, then assign that transport to outbound message chunks. If a concurrent thread removes the selected transport by unbinding an SCTP address after chunk setup but before transmission, the send path can later access freed transport data in sctp_outq_select_transport(). The race is reachable when a full send buffer causes the sending thread to temporarily release the socket lock while waiting for buffer capacity.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel SCTP use-after-free vulnerability caused by a race condition in sendmsg.
Use-after-free vulnerability in Linux kernel SCTP sendmsg processing caused by a race condition.
A Linux kernel SCTP use-after-free vulnerability caused by a race condition in sendmsg.
A Linux kernel SCTP use-after-free vulnerability caused by a race condition in sendmsg.
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.