CVE-2021-47304 is a resource-leak flaw in the Linux kernel TCP subsystem. During connection establishment, tcp_init_transfer() could clear the icsk_ca_initialized state even when congestion control had already been initialized. This permits tcp_init_congestion_control() to invoke a congestion-control module's init callback a second time without an intervening release callback. Congestion-control implementations that allocate state during initialization, including CDG, can leak that state; other module-specific effects are possible.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity Linux kernel TCP vulnerability involving tcp_init_transfer() incorrectly resetting icsk_ca_initialized. The issue was resolved by preventing that reset.
A Linux kernel TCP congestion-control initialization flaw that can cause double initialization and memory leaks when a local low-privileged process changes TCP congestion control during a TCP Fast Open connection attempt. Red Hat rates it Low severity (CVSS 5.5) with high availability impact.
A Linux kernel TCP congestion-control initialization flaw. A sequence involving TCP Fast Open/connect, changing TCP_CONGESTION while the socket is in TCP_SYN_SENT, and receiving an ACK can cause double initialization of a congestion-control module without release, potentially leaking memory.
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.