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-38471tls: always refresh the queue when reading sock

Description

In the Linux kernel, the following vulnerability has been resolved: tls: always refresh the queue when reading sock After recent changes in net-next TCP compacts skbs much more aggressively. This unearthed a bug in TLS where we may try to operate on an old skb when checking if all skbs in the queue have matching decrypt state and geometry. BUG: KASAN: slab-use-after-free in tls_strp_check_rcv+0x898/0x9a0 [tls] (net/tls/tls_strp.c:436 net/tls/tls_strp.c:530 net/tls/tls_strp.c:544) Read of size 4 at addr ffff888013085750 by task tls/13529 CPU: 2 UID: 0 PID: 13529 Comm: tls Not tainted 6.16.0-rc5-virtme Call Trace: kasan_report+0xca/0x100 tls_strp_check_rcv+0x898/0x9a0 [tls] tls_rx_rec_wait+0x2c9/0x8d0 [tls] tls_sw_recvmsg+0x40f/0x1aa0 [tls] inet_recvmsg+0x1c3/0x1f0 Always reload the queue, fast path is to have the record in the queue when we wake, anyway (IOW the path going down "if !strp->stm.full_len").

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 15 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-38471, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.47% · top 59% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0d87bbd39d7fd1135ab9eca672d760470f6508e8 – < 730fed2ff5e259495712518e18d9f521f61972bb
    • affected 0d87bbd39d7fd1135ab9eca672d760470f6508e8 – < 1f3a429c21e0e43e8b8c55d30701e91411a4df02
    • affected 0d87bbd39d7fd1135ab9eca672d760470f6508e8 – < cdb767915fc9a15d88d19d52a1455f1dc3e5ddc8
    • affected 0d87bbd39d7fd1135ab9eca672d760470f6508e8 – < c76f6f437c46b2390888e0e1dc7aafafa9f4e0c6
    • affected 0d87bbd39d7fd1135ab9eca672d760470f6508e8 – < 4ab26bce3969f8fd925fe6f6f551e4d1a508c68b
    • affected 2277d7cbdf47531b2c3cd01ba15255fa955aab35
    • affected 6.0.6 – < 6.1
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.1.147 – ≤ 6.1.*
    • unaffected 6.6.100 – ≤ 6.6.*
    • unaffected 6.12.40 – ≤ 6.12.*
    • unaffected 6.15.8 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .