CVE-2025-38471
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").
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| rhel | 9 | fixed | |
| sles | affected | | |
| debian | bookworm | fixed | 6.1.147-1 |
| debian | bullseye | fixed | 0 |
| debian | forky | fixed | 6.16.3-1 |
| debian | sid | fixed | 6.16.3-1 |
| debian | trixie | fixed | 6.12.41-1 |
| linux-kernel | affected | 6.1 | |
| linux-kernel | 6.1 | affected | |
| linux-kernel | 6.16 | affected | |
| debian | 11.0 | affected | |
| almalinux | 9 | fixed | kernel-debug-devel-5.14.0-570.35.1.el9_6.aarch64.rpm |
References
- https://access.redhat.com/errata/RHSA-2025:13962
- https://access.redhat.com/errata/RHSA-2025:14497
- https://git.kernel.org/stable/c/1f3a429c21e0e43e8b8c55d30701e91411a4df02
- https://git.kernel.org/stable/c/4ab26bce3969f8fd925fe6f6f551e4d1a508c68b
- https://git.kernel.org/stable/c/730fed2ff5e259495712518e18d9f521f61972bb
- https://git.kernel.org/stable/c/c76f6f437c46b2390888e0e1dc7aafafa9f4e0c6
- https://git.kernel.org/stable/c/cdb767915fc9a15d88d19d52a1455f1dc3e5ddc8
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://www.suse.com/security/cve/CVE-2025-38471.html
- https://security-tracker.debian.org/tracker/CVE-2025-38471
- https://bugzilla.redhat.com/2355334
- https://bugzilla.redhat.com/2366125
- https://bugzilla.redhat.com/2375303
- https://bugzilla.redhat.com/2375304
- https://bugzilla.redhat.com/2376041
- https://bugzilla.redhat.com/2376064
- https://bugzilla.redhat.com/2378982
- https://bugzilla.redhat.com/2383381
- https://bugzilla.redhat.com/2383893
- https://errata.almalinux.org/9/ALSA-2025-13962.html
CWEs
CWE-416
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.