CVE-2024-42082 is a Linux kernel XDP issue in __xdp_reg_mem_model() in net/core/xdp.c. The function used WARN() when __mem_id_init_hash_table() returned an error during XDP memory-model registration. The error condition is reachable when memory allocation fails; the alternative rhashtable initialization error path is not expected because the code uses valid static rhashtable parameters. The kernel fix removes the unnecessary WARN() handling.
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 Linux kernel XDP error-handling flaw in __xdp_reg_mem_model() in which a WARN() could be triggered on memory-allocation failure. It can cause a local denial of service through system availability impact.
Linux kernel vulnerability covered by the security update.
A Linux kernel XDP-related vulnerability involving __xdp_reg_mem_model().
A Linux kernel XDP issue in __xdp_reg_mem_model() in which a WARN() could be triggered when memory-model hash-table initialization failed due to memory-allocation failure. The fix removes the unnecessary warning path.
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.