CVE-2025-38571: Linux kernel · sunrpc: fix client side handling of tls alerts
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 8.2 High · fixed in 6.8.0-1046.49~22.04.1 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1046.49~22.04.1, 6.8.0-1051.57~22.04.1, 6.8.0-1046.53~22.04.1 +32
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7880-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7934-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-5 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2025-38571 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-38571 (opens in a new tab)
- git.kernel.org/linus/cc5d59081fa26506d02de2127ab822f40d88bc5a (opens in a new tab)
- git.kernel.org/stable/c/3ee397eaaca4fa04db21bb98c8f1d0c6cc525368 (opens in a new tab)
- git.kernel.org/stable/c/3feada5baf4dc96e151ff2ca54630e1d274e5458 (opens in a new tab)
- git.kernel.org/stable/c/a55b3d15331859d9fdd261cfa6d34ca2aeb0fb95 (opens in a new tab)
- git.kernel.org/stable/c/c36b2fbd60e8f9c6f975522130998608880c93be (opens in a new tab)
- git.kernel.org/stable/c/cc5d59081fa26506d02de2127ab822f40d88bc5a (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7880-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7934-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-5 (opens in a new tab)