CVE-2024-27014 is a deadlock vulnerability in the Linux kernel mlx5e networking driver when disabling accelerated Receive Flow Steering (aRFS). The disable operation holds priv->state_lock while calling cancel_work_sync to cancel aRFS work. If an aRFS worker has already started, cancellation waits for that worker to finish, but the worker attempts to acquire the same state lock to delete rules when the interface state is down. This circular dependency can deadlock the disable operation and worker. The affected path includes mlx5e_arfs_disable and arfs_handle_work and can be reached during channel reconfiguration through mlx5e_ethtool_set_channels.
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.
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.