Linux kernel nfsd proc registration error handling flaw
CVE-2025-22026 is a Linux kernel vulnerability in the NFS server (nfsd) initialization path. The issue is that nfsd_proc_stat_init() ignored the return value of svc_proc_register() when creating the nfsd procfs statistics entry. If svc_proc_register() failed, the failure was not propagated, leaving initialization in an inconsistent state. Later, when the kernel attempted to remove the proc entry during teardown, it could trigger a WARN because the procfile had never been created successfully. The fix changes nfsd_proc_stat_init() to return the same pointer/error semantics as svc_proc_register() and updates nfsd_net_init() to validate that result and fail nfsd network namespace construction on error. According to the provided content, svc_proc_register() can fail if a dentry cannot be allocated or if an identical dentry already exists; the latter is considered unlikely in this code path and is treated as -ENOMEM.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
3 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.
The version that knows your environment.
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.