CVE-2025-39955 is a flaw in Linux kernel TCP Fast Open handling. When tcp_disconnect() disconnects a server-side TCP Fast Open socket, it failed to clear the socket's fastopen_rsk request-socket state. If that socket is reused as a client before the original TCP Fast Open three-way handshake completes, stale state remains after the socket transitions from TCP_SYN_RECV to TCP_CLOSE. A subsequent retransmission-timer invocation can operate on the stale state, generate a kernel warning, and fail to retransmit the intended packet. The upstream correction invokes reqsk_fastopen_remove() from tcp_disconnect().
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.
35 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel TCP Fast Open state-management flaw in tcp_disconnect().
A Linux kernel TCP flaw involving failure to clear tcp_sk(sk)->fastopen_rsk during tcp_disconnect(). It is addressed by the Red Hat kernel-rt update.
Linux kernel TCP flaw involving failure to clear tcp_sk(sk)->fastopen_rsk during tcp_disconnect().
Linux kernel TCP flaw involving failure to clear the Fast Open request-socket pointer during tcp_disconnect().
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.