CVE-2024-42272 is an uninitialized-memory flaw in the Linux kernel traffic-control connection-tracking action (sched/act_ct). A change that added a network-namespace pointer to struct zones_ht_key expanded the rhashtable lookup key from two to 16 bytes. The lookup operation consequently consumed structure padding bytes that had not been initialized when tcf_ct_flow_table_get() constructed a local key. The flaw was detected by KMSAN during rhashtable lookup invoked while initializing an act_ct action.
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.
Linux kernel scheduler act_ct flaw involving padding handling in struct zones_ht_key.
A Linux kernel sched act_ct vulnerability concerning padding in the zones_ht_key structure.
A Linux kernel sched/act_ct vulnerability involving padding in the zones_ht_key structure.
A vulnerability addressed by this Red Hat Enterprise Linux 9 container-image update; no technical details are provided in the content.
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.