CVE-2023-54276 Details
Description
In the Linux kernel, the following vulnerability has been resolved: nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net Commit f5f9d4a314da ("nfsd: move reply cache initialization into nfsd startup") moved the initialization of the reply cache into nfsd startup, but didn't account for the stats counters, which can be accessed before nfsd is ever started. The result can be a NULL pointer dereference when someone accesses /proc/fs/nfsd/reply_cache_stats while nfsd is still shut down. This is a regression and a user-triggerable oops in the right situation: - non-x86_64 arch - /proc/fs/nfsd is mounted in the namespace - nfsd is not started in the namespace - unprivileged user calls "cat /proc/fs/nfsd/reply_cache_stats" Although this is easy to trigger on some arches (like aarch64), on x86_64, calling this_cpu_ptr(NULL) evidently returns a pointer to the fixed_percpu_data. That struct looks just enough like a newly initialized percpu var to allow nfsd_reply_cache_stats_show to access it without Oopsing. Move the initialization of the per-net+per-cpu reply-cache counters back into nfsd_init_net, while leaving the rest of the reply cache allocations to be done at nfsd startup time. Kudos to Eirik who did most of the legwork to track this down.
A vulnerability in the Linux kernel's NFS server implementation can lead to a NULL pointer dereference. This issue arises because the initialization of per-network, per-CPU reply cache statistics counters was moved to the NFS server startup process, without properly accounting for the statistics counters. As a result, an unprivileged user can trigger a crash by accessing the reply cache statistics file in the proc filesystem while the NFS server is not running. This vulnerability affects non-x86_64 architectures, such as aarch64, and has been identified as a regression.
The vulnerability has been addressed by moving the initialization of the reply cache statistics counters back to the NFS server initialization function, ensuring that the counters are properly set up before they are accessed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 30, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/3025d489f9c8984d1bf5916c4a20097ed80fca5c | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/66a178177b2b3bb1d71e854c5e7bbb320eb0e566 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/768c408594b52d8531e1a8ab62e5620c19213e73 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/8549384d0f65981761fe2077d04fa2a8d37b54e0 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/ed9ab7346e908496816cffdecd46932035f66e2e | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | >= 6.3, < 6.3.0-rc1 |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 30, 2025 | New CVE Received | kernel.org |
Volerion