Loading vulnerability…
CVE-2022-50053 is a deadlock vulnerability in the Linux kernel Intel Adaptive Virtual Function (iavf) network driver. In the reset-task error path, iavf_reset_task could call iavf_close. This may invoke napi_disable a second time, causing a deadlock. The deadlocked close path retains crit_lock, while iavf_remove requires the same lock, causing virtual-function removal to hang. The condition is associated with rapid virtual-function resets and failure to initialize the VF mailbox. The corrected error path invokes iavf_disable_vf to clean up invalid resources rather than calling iavf_close.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in the iavf driver reset error handling that can trigger a double napi_disable call, causing deadlock and potentially leaving iavf_remove stuck, leading to hung tasks and kernel panic.
A Linux kernel iavf vulnerability described in the advisory as a reset error handling issue.
A Linux kernel iavf driver error-handling flaw in which iavf_close may invoke napi_disable twice during iavf_reset_task processing, resulting in a deadlock and denial of service.
A Linux kernel iavf flaw described in the advisory as a reset error handling issue.
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.