CVE-2025-22026

nfsd: don't ignore the return code of svc_proc_register()

MEDIUM
5.5
CVSS Score
Published: April 16, 2025 at 02:11 PM UTC
Updated: June 20, 2026 at 03:50 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.8.10v < 6.12.245.10.226 ≤ v < 5.10.2595.15.166 ≤ v < 5.15.2106.1.106 ≤ v < 6.1.1646.13 ≤ v < 6.13.126.14 ≤ v < 6.14.26.6.47 ≤ v < 6.6.1256.8.10 ≤ v < 6.96.9 ≤ v < 6.12.246.9 ≤ v < 6.13.126.9 ≤ v < 6.14.26.9 ≤ v < 6.1510ece754df9a799131a1cf3197e9d26c04ddec225.10.2265.15.1665545496966631cd40ad3aa6450be56d0e5773d106.1.1066.6.476.8.106.96f8d6ed3426a17f77628cebfb6a6e2c6f2b2496c73c43bccf25cec9cdec62fc22a513c28a4b2839093483ac5fec62cc1de166051b219d953bb5e4ef4b7b05f98f3f06fea3986b46e5c7fe2928676b02d
Vendor states this is fixed in 30405b23b4d5e2a596fb756d48119d7293194e75 (fixed)
Vendor states this is fixed in 51107e768de6821b68aa34a136d07bc7a09cf6c3 (fixed)
Vendor states this is fixed in 51da899c209a9624e48be416bd30e7ed5cd6c3d8 (fixed)
Vendor states this is fixed in 6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0 (fixed)
Vendor states this is fixed in 930b64ca0c511521f0abdd1d57ce52b2a6e3476b (fixed)
Vendor states this is fixed in 9d9456185fd5f1891c74354ee297f19538141ead (fixed)
Vendor states this is fixed in e31957a819e60cf0bc9a49408765e6095fd3d046 (fixed)
Vendor states this is fixed in e4316bd85e42b01125b2aab691769234a388b8a3 (fixed)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.164 (unaffected)
Vendor states this is fixed in 6.12.24 (unaffected)
Vendor states this is fixed in 6.13.12 (unaffected)
Vendor states this is fixed in 6.14.2 (unaffected)
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.6.125 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-252

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card