CVE-2025-22026
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| โ | Affected | โ |
AlmaLinux Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | kernel-devel-5.14.0-570.55.1.el9_6.aarch64.rpm |
| 8 | Fixed | kernel-rt-debug-modules-extra-4.18.0-553.77.1.rt7.418.el8_10.x86_64.rpm |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 6.12.25-1 |
| sid | Fixed | 6.12.25-1 |
| forky | Fixed | 6.12.25-1 |
| bullseye | Fixed | 6.1.164-1~deb11u1 |
| bookworm | Fixed | 6.1.164-1 |
Red Hat Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | โ |
| 8 | Fixed | โ |
Rocky Linux Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 8 | Fixed | โ |
References
- https://access.redhat.com/errata/RHSA-2025:18281
- https://errata.rockylinux.org/RLSA-2025:16920
- https://errata.rockylinux.org/RLSA-2025:16919
- https://www.suse.com/security/cve/CVE-2025-22026.html
- https://security-tracker.debian.org/tracker/CVE-2025-22026
- https://access.redhat.com/errata/RHSA-2025:16919
- https://bugzilla.redhat.com/2360224
- https://bugzilla.redhat.com/2363672
- https://bugzilla.redhat.com/2373539
- https://bugzilla.redhat.com/2393166
- https://errata.almalinux.org/8/ALSA-2025-16919.html
- https://access.redhat.com/errata/RHSA-2025:16920
- https://errata.almalinux.org/8/ALSA-2025-16920.html
- https://bugzilla.redhat.com/2389480
- https://bugzilla.redhat.com/2389487
- https://bugzilla.redhat.com/2395805
- https://bugzilla.redhat.com/2396928
- https://bugzilla.redhat.com/2396944
- https://errata.almalinux.org/9/ALSA-2025-18281.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.