LiveActive security incident?Get immediate response
CVE Record

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

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.
Prepared
Confidence
medium
Sources
7

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-38430Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxed94164398c935a42be7b129a478eb19c598b68a, ed94164398c935a42be7b129a478eb19c598b68a, ed94164398c935a42be7b129a478eb19c598b68a, ed94164398c935a42be7b129a478eb19c598b68a, ed94164398c935a42be7b129a478eb19c598b68a, ed94164398c935a42be7b129a478eb19c598b68a, ed94164398c935a42be7b129a478eb19c598b68a, ed94164398c935a42be7b129a478eb19c598b68aunaffected
LinuxLinux4.8, 0, 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.