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-38616tls: handle data disappearing from under the TLS ULP

Description

In the Linux kernel, the following vulnerability has been resolved: tls: handle data disappearing from under the TLS ULP TLS expects that it owns the receive queue of the TCP socket. This cannot be guaranteed in case the reader of the TCP socket entered before the TLS ULP was installed, or uses some non-standard read API (eg. zerocopy ones). Replace the WARN_ON() and a buggy early exit (which leaves anchor pointing to a freed skb) with real error handling. Wipe the parsing state and tell the reader to retry. We already reload the anchor every time we (re)acquire the socket lock, so the only condition we need to avoid is an out of bounds read (not having enough bytes in the socket for previously parsed record len). If some data was read from under TLS but there's enough in the queue we'll reload and decrypt what is most likely not a valid TLS record. Leading to some undefined behavior from TLS perspective (corrupting a stream? missing an alert? missing an attack?) but no kernel crash should take place.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 12 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-38616, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · 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 7.8.

Affected products

  • Linux · Linux

    • affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < ef50eaab631f9bf519ddbdfa42ccb0528adc1fc8
    • affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < f1fe99919f629f980d0b8a7ff16950bffe06a859
    • affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < eb0336f213fe88bbdb7d2b19c9c9ec19245a3155
    • affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < db3658a12d5ec4db7185ae7476151a50521b7207
    • affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < 2fb97ed9e2672b4f6e24ce206ac1a875ce4bcb38
    • affected 84c61fe1a75b4255df1e1e7c054c9e6d048da417 – < 6db015fc4b5d5f63a64a193f65d98da3a7fc811d
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .