Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38571sunrpc: fix client side handling of tls alerts

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38571, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.37% · top 69% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

  • Linux · Linux

    • affected dea034b963c8901bdcc3d3880c04f0d75c95112f – < a55b3d15331859d9fdd261cfa6d34ca2aeb0fb95
    • affected dea034b963c8901bdcc3d3880c04f0d75c95112f – < c36b2fbd60e8f9c6f975522130998608880c93be
    • affected dea034b963c8901bdcc3d3880c04f0d75c95112f – < 3ee397eaaca4fa04db21bb98c8f1d0c6cc525368
    • affected dea034b963c8901bdcc3d3880c04f0d75c95112f – < 3feada5baf4dc96e151ff2ca54630e1d274e5458
    • affected dea034b963c8901bdcc3d3880c04f0d75c95112f – < cc5d59081fa26506d02de2127ab822f40d88bc5a
  • Linux · Linux

    • affected 6.5
    • unaffected < 6.5
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38571 badge
[![CVE-2025-38571](https://cveledger.app/badge/CVE-2025-38571.svg)](https://cveledger.app/cve/CVE-2025-38571)

Record last updated .