Loading vulnerability…
CVE-2024-27014 is a deadlock vulnerability in the Linux kernel mlx5e network-driver implementation of accelerated Receive Flow Steering (aRFS). When aRFS is disabled while priv->state_lock is held, the disable path synchronously cancels scheduled aRFS work. If an aRFS worker is already executing, cancellation waits for that worker to finish; the worker can in turn attempt to acquire the already-held state lock, producing a circular lock dependency. The fix introduces explicit aRFS enabled-state tracking, prevents rule additions after aRFS is disabled, and removes the worker's inappropriate responsibility for deleting rules during the down-state transition.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel mlx5e network-driver deadlock vulnerability while disabling aRFS.
Linux kernel mlx5e adaptive receive-flow-steering disablement deadlock.
Linux kernel mlx5e network-driver deadlock vulnerability while disabling accelerated receive flow steering.
Linux kernel mlx5e adaptive receive-flow-steering deadlock vulnerability.
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.