CVE-2025-38566: sunrpc: fix handling of server side tls alerts
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: fix handling of server side tls alerts
Scott Mayhew discovered a security exploit in NFS over TLS in
tls_alert_recv() due to its assumption it can read data from
the msg iterator's kvec..
kTLS implementation splits TLS non-data record payload between
the control message buffer (which includes the type such as TLS
aler or TLS cipher change) and the rest of the payload (say TLS
alert's level/description) which goes into the msg payload buffer.
This patch proposes to rework how control messages are setup and
used by sock_recvmsg().
If no control message structure is setup, kTLS layer will read and
process TLS data record types. As soon as it encounters a TLS control
message, it would return an error. At that point, NFS can setup a
kvec backed msg buffer and read in the control message such as a
TLS alert. Msg iterator can advance the kvec pointer as a part of
the copy process thus we need to revert the iterator before calling
into the tls_alert_recv.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux NFS over TLS mishandles TLS alerts because kernel code makes an unsafe assumption about a message iterator. The supplied record rates it CVSS 9.8, indicating potentially severe impact. However, the sources do not specify the demonstrated security consequence, so remote code execution or another particular outcome should not be assumed.
Executive priority
Treat this as urgent where NFS over TLS is enabled, especially across untrusted or large network segments. Begin with rapid exposure inventory, then apply supported kernel updates. Systems not using NFS over TLS have lower apparent exposure, but teams should verify configuration rather than assume they are unaffected.
Technical view
The sunrpc NFS-over-TLS path incorrectly assumes tls_alert_recv() can read from the message iterator’s kvec. kTLS divides control-record information and payload across separate buffers, and copying can advance the iterator. The fix restructures control-message handling and reverts the iterator before processing a TLS alert.
Likely exposure
Exposure is limited to Linux systems using NFS over TLS on affected kernels. The metadata lists 6.4, 6.6.102, 6.12.42, 6.15.10, 6.16.1, and 6.17, plus an ambiguous “0” entry. Confirm affected ranges and backports with the relevant Linux distribution or kernel vendor.
Exploitation context
The description says a security exploit was discovered, but the supplied sources do not establish public exploitation or attacks in the wild. The record is not marked as included in CISA KEV. No exploit mechanism, proof of concept, or concrete impact primitive is provided in the bundle.
Researcher notes
The supplied description identifies iterator-state and buffer-layout handling as the root issue but provides no CWE, crash signature, memory-corruption classification, or proven confidentiality, integrity, and availability primitive. Review the linked stable commits for branch-specific remediation details. Avoid inferring remote code execution solely from the 9.8 CVSS vector.
Mitigation direction
Identify Linux systems using NFS over TLS and prioritize broadly reachable deployments.
Check kernel or distribution advisories for an update containing the applicable referenced fix.
Install the vendor-supported fixed kernel and reboot where required to activate it.
Until updated, restrict affected NFS-over-TLS access to explicitly trusted systems.
Validation and detection
Record each system’s running kernel build and whether NFS over TLS is enabled.
Compare builds against vendor advisories because the bundled version metadata is incomplete or ambiguous.
Verify the installed kernel contains the applicable stable fix or vendor backport.
After rebooting, confirm the fixed kernel is running and NFS-over-TLS operations remain functional.
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-38566 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
0ADP providers
6Source 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.