Loading vulnerability…
CVE-2024-39502 is a use-after-free flaw in the Linux kernel's Pensando/AMD ionic network driver. The bug occurs in queue/NAPI lifecycle handling when queue counts are reconfigured. During queue startup, the driver uses netif_napi_add() and napi_enable() for active queues. However, ionic_qcq_enable() relies on the NAPI .poll pointer being non-NULL to decide whether a queue's NAPI instance should be enabled. After netif_napi_del(), the .poll pointer is not reset to NULL, so the driver can misidentify an unregistered NAPI instance as still valid and call napi_enable() on it. This creates a stale-object/use-after-free condition and can trigger a kernel BUG in napi_enable(). The issue is reproducible by changing RX/TX/combined queue counts with ethtool in a sequence that unregisters and later re-enables queues.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.