Loading vulnerability…
CVE-2024-35907 is a NULL-pointer dereference in the Linux kernel mlxbf_gige Ethernet driver. The driver registered its RX interrupt with request_irq() before initializing its NAPI context. If an RX interrupt was already pending, the interrupt could fire immediately after registration and schedule NAPI polling before the poll callback had been initialized, leading to execution through a NULL function pointer. The issue was observed when the driver was loaded and its interface brought up in a kdump kernel. The fix initializes NAPI before requesting IRQs.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel mlxbf_gige network-driver initialization-order issue involving request_irq() and NAPI.
Linux kernel mlxbf_gige Ethernet driver initialization-order flaw involving request_irq() and NAPI.
An initialization-order flaw in the Linux kernel mlxbf_gige network driver, where IRQ registration occurred before NAPI initialization.
Linux kernel mlxbf_gige driver initialization-order flaw affecting IRQ registration and NAPI initialization.
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.