Loading vulnerability…
CVE-2020-25212 is a time-of-check/time-of-use mismatch in the Linux kernel NFSv4 client in versions before 5.8.3. A size validation is performed separately from the NFSv4 XDR response processing that relies on that value, allowing inconsistent handling of a crafted response from an NFS server. An attacker-controlled NFSv4 server can exploit the mismatch to cause memory corruption in a client that mounts the server.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Time-of-check/time-of-use mismatch vulnerability in Linux kernel NFS client code.
Time-of-check to time-of-use race condition in Linux kernel NFS client code.
Linux kernel NFS client time-of-check to time-of-use (TOCTOU) mismatch flaw.
Linux kernel time-of-check/time-of-use mismatch in NFS client code.
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.