CVE-2025-22026 is a Linux kernel flaw in the NFS server subsystem (nfsd) caused by improper handling of the return value from svc_proc_register() during procfs statistics initialization. In the vulnerable code path, nfsd_proc_stat_init() ignored failures from svc_proc_register(), allowing nfsd network namespace initialization to proceed even when procfile registration had failed. Later cleanup could then attempt to remove an entry that was never successfully created, triggering a kernel WARN. The fix changes nfsd_proc_stat_init() to propagate the pointer/error result from svc_proc_register() and updates nfsd_net_init() to abort nfsd network namespace construction when registration fails. Failure conditions include dentry allocation failure and, less likely, attempted creation of an already existing identical dentry.
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.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.