Answer in brief
CVE-2025-22026 records a Medium severity (CVSS 5.5) vulnerability in nfsd: don't ignore the return code of svc_proc_register(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-22026 records a Medium severity (CVSS 5.5) vulnerability in nfsd: don't ignore the return code of svc_proc_register(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5545496966631cd40ad3aa6450be56d0e5773d10 <51107e768de6821b68aa34a136d07bc7a09cf6c3 || >=73c43bccf25cec9cdec62fc22a513c28a4b28390 <e4316bd85e42b01125b2aab691769234a388b8a3 || >=10ece754df9a799131a1cf3197e9d26c04ddec22 <51da899c209a9624e48be416bd30e7ed5cd6c3d8 || >=6f8d6ed3426a17f77628cebfb6a6e2c6f2b2496c <30405b23b4d5e2a596fb756d48119d7293194e75 || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0 || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <e31957a819e60cf0bc9a49408765e6095fd3d046 || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <9d9456185fd5f1891c74354ee297f19538141ead || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <930b64ca0c511521f0abdd1d57ce52b2a6e3476b || b7b05f98f3f06fea3986b46e5c7fe2928676b02d || >=5.10.226 <5.10.259 || >=5.15.166 <5.15.210 || >=6.1.106 <6.1.164 || >=6.6.47 <6.6.125 || >=6.8.10 <6.9 | 51107e768de6821b68aa34a136d07bc7a09cf6c3, e4316bd85e42b01125b2aab691769234a388b8a3, 51da899c209a9624e48be416bd30e7ed5cd6c3d8, 30405b23b4d5e2a596fb756d48119d7293194e75, 6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0, e31957a819e60cf0bc9a49408765e6095fd3d046, 9d9456185fd5f1891c74354ee297f19538141ead, 930b64ca0c511521f0abdd1d57ce52b2a6e3476b, 5.10.259, 5.15.210, 6.1.164, 6.6.125, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5545496966631cd40ad3aa6450be56d0e5773d10 <51107e768de6821b68aa34a136d07bc7a09cf6c3 || >=73c43bccf25cec9cdec62fc22a513c28a4b28390 <e4316bd85e42b01125b2aab691769234a388b8a3 || >=10ece754df9a799131a1cf3197e9d26c04ddec22 <51da899c209a9624e48be416bd30e7ed5cd6c3d8 || >=6f8d6ed3426a17f77628cebfb6a6e2c6f2b2496c <30405b23b4d5e2a596fb756d48119d7293194e75 || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0 || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <e31957a819e60cf0bc9a49408765e6095fd3d046 || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <9d9456185fd5f1891c74354ee297f19538141ead || >=93483ac5fec62cc1de166051b219d953bb5e4ef4 <930b64ca0c511521f0abdd1d57ce52b2a6e3476b || b7b05f98f3f06fea3986b46e5c7fe2928676b02d || >=5.10.226 <5.10.259 || >=5.15.166 <5.15.210 || >=6.1.106 <6.1.164 || >=6.6.47 <6.6.125 || >=6.8.10 <6.9 | 51107e768de6821b68aa34a136d07bc7a09cf6c3, e4316bd85e42b01125b2aab691769234a388b8a3, 51da899c209a9624e48be416bd30e7ed5cd6c3d8, 30405b23b4d5e2a596fb756d48119d7293194e75, 6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0, e31957a819e60cf0bc9a49408765e6095fd3d046, 9d9456185fd5f1891c74354ee297f19538141ead, 930b64ca0c511521f0abdd1d57ce52b2a6e3476b, 5.10.259, 5.15.210, 6.1.164, 6.6.125, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.