Loading vulnerability…
CVE-2024-35960 is a Linux kernel flaw in the net/mlx5 flow-steering rule-management logic. Before the fix, add_rule_fg() linked a newly created rule into the rule tree only when its reference count was one. During create_flow_handle(), an identical newly created rule could be referenced again while the same flow handle was being created. The rule could therefore have a reference count of two while remaining unlinked, with NULL parent and root pointers. When the corresponding flow group is deleted, del_sw_hw_rule() dereferences the assumed non-NULL parent pointer and crashes the kernel. The corrective change links new parentless rules into the tree and initializes them properly.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel net/mlx5 flow-steering rule-management vulnerability. Improper linking of newly created rules into the flow-steering tree can cause a kernel crash when an affected flow group is deleted. Google COS packages sys-kernel/csql-kernel-6_1 and sys-kernel/lakitu-kernel-6_1 are affected; version 18244.85.5 or later remediates it.
Linux kernel mlx5 driver flaw in linking newly created flow-steering rules into the rule tree.
An incorrect flow-steering rule tree linkage issue in the Linux kernel mlx5 driver.
Linux kernel mlx5 driver vulnerability involving improper linking of new flow-steering rules into the tree.
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.