CVE-2024-35959 affects the Linux kernel mlx5e network driver initialization-failure cleanup path. If mlx5e_priv_init() fails, its cleanup invokes mlx5e_selq_cleanup(), which invokes selector-queue application logic requiring priv->state_lock to be held. The affected cleanup path did not acquire that lock, causing suspicious protected RCU dereference/lockdep warnings. The upstream correction acquires state_lock in mlx5e_selq_cleanup().
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A cleanup-flow flaw in Linux kernel mlx5e private-context initialization.
A flaw in cleanup processing in the Linux kernel mlx5e network driver initialization routine.
Linux kernel mlx5e private-initialization cleanup-flow vulnerability.
Linux kernel Mellanox mlx5e private-initialization cleanup-flow flaw.
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.