CVE-2025-38430: nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request
In the Linux kernel, the following vulnerability has been resolved:
nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request
If the request being processed is not a v4 compound request, then
examining the cstate can have undefined results.
This patch adds a check that the rpc procedure being executed
(rq_procinfo) is the NFSPROC4_COMPOUND procedure.
Security readout for executives and security teams
Plain-English summary
A Linux NFS server can examine invalid request state when processing something other than an NFSv4 compound request. The supplied score rates potential impact as critical, but the sources do not document demonstrated confidentiality, integrity, or availability consequences. Systems providing NFS services on affected kernels warrant prompt review.
Executive priority
Treat internet-accessible or broadly reachable NFS servers as urgent patching candidates. Prioritize exposed production storage and appliances, then internally restricted servers. The critical score justifies rapid action, although current evidence does not establish active attacks or confirmed real-world impact.
Technical view
The kernel function nfsd4_spo_must_allow() could inspect compound-state data without first confirming the current RPC procedure is NFSPROC4_COMPOUND, producing undefined results. The stable fix adds that procedure check. Exact runtime consequences are not described in the supplied evidence.
Likely exposure
Potential exposure is limited to Linux systems running the NFS server implementation on affected kernel builds. Network accessibility increases concern. Distribution backports may change whether a reported kernel version is vulnerable, so package-specific advisories and changelogs must be checked.
Exploitation context
The CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. The 9.8 CVSS vector describes unauthenticated, low-complexity network reachability, but demonstrated exploitability and practical impact remain unclear.
Researcher notes
The key invariant is that compound state must only be examined for NFSPROC4_COMPOUND. Review vendor backports rather than relying solely on upstream version strings. The supplied affected-version data contains duplicated commit entries and does not clearly map every stable commit to a release, limiting precise exposure conclusions.
Mitigation direction
Install a vendor-supported kernel update containing the applicable stable fix.
Review distribution and appliance advisories for backported fixes and required versions.
Restrict NFS and RPC access to trusted networks while updates are pending.
Do not treat network restriction as a substitute for patching.
Validation and detection
Inventory hosts providing NFS services and record their running kernel builds.
Confirm whether nfsd is active and which networks can reach NFS or RPC services.
Map each kernel package to vendor advisories or the supplied stable commits.
After updating, verify the fixed kernel is running and rescan affected assets.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38430 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
12Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.