CVE-2022-49316 is an improper-locking flaw in the Linux kernel NFSv4 implementation. During layoutget processing performed as part of an open() compound operation, layoutget locks can remain held when subsequent RPC calls are made. A subsequent operation such as setattr() can trigger an NFS recall; processing that recall while the layout locks are retained can deadlock.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel vulnerability addressed by the advisory; no flaw description is provided in the content.
A Linux kernel NFSv4 improper-locking vulnerability that can cause a deadlock and denial of service. It is rated Moderate with CVSS v3.1 5.5 (local, low complexity, low privileges required, no user interaction, high availability impact).
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.