CVE-2025-22026: nfsd: don't ignore the return code of svc_proc_register()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 30405b23b4d5e2a596fb756d48119d7293194e75, 5.10.259, 5.15.210; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.126.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 30405b23b4d5e2a596fb756d48119d7293194e75, 5.10.259, 5.15.210; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.126.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-01408
- ALSA-2025:16919
- ALSA-2025:16920
- ALSA-2025:17396
- ALSA-2025:18281
- DLA-4499-1
- DSA-6163-1
- RHSA-2025:13946
- RHSA-2025:14003
- RHSA-2025:14005
- RHSA-2025:14744
- RHSA-2025:14749
- RHSA-2025:16919
- RHSA-2025:16920
- RHSA-2025:17396
- RHSA-2025:18281
- RHSA-2025:18932
- RHSA-2025:19222
- RHSA-2025:21063
- RHSA-2025:21082
- Published
- Apr 16, 2025
- Updated
- Jun 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-252
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.12.24
- linux linux kernel6.13 and later · before 6.13.12
- linux linux kernel6.14 and later · before 6.14.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- b7b05f98f3f06fea3986b46e5c7fe2928676b02d, 6.9affected
- 5545496966631cd40ad3aa6450be56d0e5773d10 and later · before 51107e768de6821b68aa34a136d07bc7a09cf6c3affected · git
- 73c43bccf25cec9cdec62fc22a513c28a4b28390 and later · before e4316bd85e42b01125b2aab691769234a388b8a3affected · git
- 10ece754df9a799131a1cf3197e9d26c04ddec22 and later · before 51da899c209a9624e48be416bd30e7ed5cd6c3d8affected · git
- 6f8d6ed3426a17f77628cebfb6a6e2c6f2b2496c and later · before 30405b23b4d5e2a596fb756d48119d7293194e75affected · git
- 93483ac5fec62cc1de166051b219d953bb5e4ef4 and later · before 6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0affected · git
- 93483ac5fec62cc1de166051b219d953bb5e4ef4 and later · before e31957a819e60cf0bc9a49408765e6095fd3d046affected · git
- 93483ac5fec62cc1de166051b219d953bb5e4ef4 and later · before 9d9456185fd5f1891c74354ee297f19538141eadaffected · git
- 93483ac5fec62cc1de166051b219d953bb5e4ef4 and later · before 930b64ca0c511521f0abdd1d57ce52b2a6e3476baffected · git
- 5.10.226 and later · before 5.10.259affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.38.1.el10_0 | 6.12.0-55.38.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.38.1.el10_0 | 6.12.0-55.38.1.el10_0 |
| AlmaLinux:8 | bpftool | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.77.1.el8_10 | 4.18.0-553.77.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.77.1.rt7.418.el8_10 | 4.18.0-553.77.1.rt7.418.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.77.1.rt7.418.el8_10 | 4.18.0-553.77.1.rt7.418.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.77.1.rt7.418.el8_10 | 4.18.0-553.77.1.rt7.418.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.77.1.rt7.418.el8_10 | 4.18.0-553.77.1.rt7.418.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.77.1.rt7.418.el8_10 | 4.18.0-553.77.1.rt7.418.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.77.1.rt7.418.el8_10 | 4.18.0-553.77.1.rt7.418.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.77.1.rt7.418.el8_10 | 4.18.0-553.77.1.rt7.418.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-58097Apr 16, 2025 · wifi: ath11k: fix RCU stall while reaping monitor destination ring22Monitor
- ← EarlierCVE-2025-22024Apr 16, 2025 · nfsd: fix management of listener transports22Monitor
- Later →CVE-2025-22027Apr 16, 2025 · media: streamzap: fix race between device disconnection and urb callback18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 30405b23b4d5e2a596fb756d48119d7293194e75 | Vendor (CNA) |
| Linux Linux | 5.10.259 | Vendor (CNA) |
| Linux Linux | 5.15.210 | Vendor (CNA) |
| Linux Linux | 51107e768de6821b68aa34a136d07bc7a09cf6c3 | Vendor (CNA) |
| Linux Linux | 51da899c209a9624e48be416bd30e7ed5cd6c3d8 | Vendor (CNA) |
| Linux Linux | 6.1.164 | Vendor (CNA) |
| Linux Linux | 6.6.125 | Vendor (CNA) |
| Linux Linux | 6.9 | Vendor (CNA) |
| Linux Linux | 6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0 | Vendor (CNA) |
| Linux Linux | 930b64ca0c511521f0abdd1d57ce52b2a6e3476b | Vendor (CNA) |
| Linux Linux | 9d9456185fd5f1891c74354ee297f19538141ead | Vendor (CNA) |
| Linux Linux | e31957a819e60cf0bc9a49408765e6095fd3d046 | Vendor (CNA) |
| Linux Linux | e4316bd85e42b01125b2aab691769234a388b8a3 | Vendor (CNA) |
| azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 | 6.6.126.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.77.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.164-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.164-1~deb11u1 · Debian:11 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.83.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
+13
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-39492280 days apartmailbox: mtk-cmdq: Fix pm_runtime_get_sync() warning in mbox shutdown28Monitor
- CVE-2023-5307016 days apartACPI: PPTT: Fix to avoid sleep in the atomic context when PPTT is absent22Monitor
- CVE-2025-38602125 days apartiwlwifi: Add missing check for alloc_ordered_workqueue22Monitor
- CVE-2024-42067261 days apartbpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()22Monitor
- CVE-2024-42068261 days apartbpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()22Monitor
- CVE-2023-52797330 days apartdrivers: perf: Check find_first_bit() return value22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-252 · Unchecked Return ValueCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/e4316bd85e42b01125b2aab691769234a388b8a3
- git.kernel.org/stable/c/30405b23b4d5e2a596fb756d48119d7293194e75
- git.kernel.org/stable/c/51107e768de6821b68aa34a136d07bc7a09cf6c3
- git.kernel.org/stable/c/51da899c209a9624e48be416bd30e7ed5cd6c3d8
- git.kernel.org/stable/c/6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0
- git.kernel.org/stable/c/930b64ca0c511521f0abdd1d57ce52b2a6e3476b
- git.kernel.org/stable/c/9d9456185fd5f1891c74354ee297f19538141ead
Vendor advisories and official records. Exploit/PoC links are deliberately left out.