Loading vulnerability…
CVE-2025-40251 is a dangling-pointer flaw in the Linux kernel devlink rate subsystem. During destruction of devlink rate nodes, devl_rate_nodes_destroy notified driver-specific parent-setting operations and decremented the parent reference count but did not clear the devlink_rate parent pointer. Subsequent teardown could retain and act on the stale parent relationship, producing refcount underflow warnings and memory leaks. The defect was reproduced with netdevsim and mlx5 rate-object teardown flows.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel devlink rate handling vulnerability involving parent pointer cleanup in devl_rate_nodes_destroy.
A Linux kernel devlink rate handling vulnerability involving parent pointer cleanup in devl_rate_nodes_destroy.
A Linux kernel devlink rate-management flaw in which a parent pointer is not unset during devl_rate_nodes_destroy.
A Linux kernel devlink rate-node cleanup flaw involving an unset parent pointer in devl_rate_nodes_destroy.
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.