CVE-2025-38430: nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request

Published Jul 25, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

nfsd: nfsd4spomustallow() 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 (rqprocinfo) is the NFSPROC4COMPOUND procedure.

Affected Software

11 affected componentsFixes available
Linux Kernel
Linux Linux kernel<5.4.295
Linux Linux kernel>=5.5<5.10.239
Linux Linux kernel>=5.11<5.15.186
Linux Linux kernel>=5.16<6.1.142
Linux Linux kernel>=6.2<6.6.95
Linux Linux kernel>=6.7<6.12.35
Linux Linux kernel>=6.13<6.15.4
Debian Debian Linux=11.0
Microsoft azl3 kernel 6.6.92.2-2
Microsoft azl3 kernel 6.6.96.1-1

Event History

Jul 25, 2025
CVE Published
via MITRE·02:16 PM
Data Sourced
via MITRE·02:16 PM
DescriptionSeverity
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityAffected Software
Aug 7, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-38430?

CVE-2025-38430 has been categorized with a moderate severity due to potential undefined behavior in processing NFSv4 compound requests.

2

How do I fix CVE-2025-38430?

You can resolve CVE-2025-38430 by applying the latest patches provided by the Linux kernel maintainers that address the vulnerability.

3

What systems are affected by CVE-2025-38430?

CVE-2025-38430 affects systems running vulnerable versions of the Linux Kernel that include the NFS server functionality.

4

What is the main issue caused by CVE-2025-38430?

The main issue caused by CVE-2025-38430 is the potential for undefined results when examining the cstate in non-v4 compound requests.

5

When was CVE-2025-38430 resolved?

CVE-2025-38430 was resolved with a patch that introduced necessary checks for processing NFSv4 compound requests.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203