CVE-2025-38571: sunrpc: fix client side handling of tls alerts
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: fix client side handling of tls alerts
A security exploit was discovered in NFS over TLS in tls_alert_recv
due to its assumption that there is valid data in the msghdr's
iterator's kvec.
Instead, this patch proposes the 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 control buffer and read in the control message such as a TLS
alert. Scott found that a 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 Linux NFS-over-TLS client can mishandle a TLS alert because kernel code assumes a message buffer remains in a valid position. The supplied CVSS score is 8.2, reflecting network-reachable, low-complexity impact with potentially serious service disruption and limited confidentiality loss. Exposure is confined to affected kernels using NFS over TLS.
Executive priority
Treat as a high-priority kernel remediation for environments using NFS over TLS, especially business-critical storage clients. Establish exposure quickly, then patch through supported distribution channels. Broad emergency action across Linux systems is not justified by this bundle alone because the vulnerable path is feature-specific and active exploitation is unconfirmed.
Technical view
The flaw is in sunrpc tls_alert_recv handling. A receive operation can advance the msghdr iterator’s kvec pointer; calling tls_alert_recv without first reverting that iterator may process an invalid position. The kernel fixes rework control-message handling around sock_recvmsg and restore the iterator before reading a TLS alert.
Likely exposure
Prioritize Linux systems operating as NFS-over-TLS clients. The bundle identifies affected kernel versions but does not preserve clear range semantics, so the exact vulnerable-to-fixed boundary cannot be determined reliably from its flattened version list. Systems not using NFS over TLS are less likely to reach this code path.
Exploitation context
The record describes a discovered security exploit, but supplies no public exploit details or evidence of exploitation in the wild. It is not marked as included in CISA KEV. The network vector and absence of required privileges or user interaction increase concern where an affected NFS-over-TLS client communicates with untrusted or compromised endpoints.
Researcher notes
The provided affected-version data appears flattened and includes ambiguous entries, including “0”; do not infer precise ranges from it. Review the CVE List V5 record and stable-branch commits for branch-specific boundaries. No CWE is assigned. The supplied vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable Linux stable fix.
Check distribution advisories for exact vulnerable and fixed package versions.
Prioritize exposed NFS-over-TLS clients and systems where storage disruption has high business impact.
Restrict NFS-over-TLS connections to trusted, authorized endpoints while remediation is pending.
Validation and detection
Inventory Linux hosts configured as NFS-over-TLS clients.
Record each host’s running kernel and distribution package version.
Confirm fix inclusion through distribution advisories or the referenced stable commits.
Retest NFS-over-TLS connectivity after updating and review relevant kernel logs.
Verify hosts booted into the updated kernel rather than retaining the vulnerable runtime.
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-38571 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.