Loading vulnerability…
CVE-2024-36904 is a race condition in Linux kernel TCP TIME-WAIT socket handling. inet_twsk_hashdance() inserts a TIME-WAIT socket into the established-socket hash table and releases the bucket lock before initializing its reference count. A concurrent connection path can find that socket through tcp_twsk_unique() while its reference count remains zero. tcp_twsk_unique() previously acquired a reference unconditionally, causing a reference-count increment on zero. The later reference-count initialization can overwrite the saturated invalid count, leaving an unbalanced count and allowing the socket to be freed prematurely. This creates a use-after-free condition, including in the TIME-WAIT socket release path. The upstream correction uses refcount_inc_not_zero() in tcp_twsk_unique() and declines port reuse when a valid reference cannot be acquired.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Reference-count handling flaw in Linux kernel TCP time-wait socket processing.
Linux kernel TCP reference-counting flaw in tcp_twsk_unique().
Linux kernel TCP reference-count handling issue in tcp_twsk_unique().
Linux kernel TCP time-wait socket reference-counting flaw.
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.