CVE-2025-38471: tls: always refresh the queue when reading sock
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").
Security readout for executives and security teams
Plain-English summary
A Linux kernel TLS receive-path flaw can read memory after it has been freed when TCP reorganizes queued network data. This can cause kernel instability and may affect confidentiality or integrity, but the supplied evidence does not demonstrate code execution or real-world attacks.
Executive priority
Treat remediation as urgent where affected kernels use kernel TLS, especially on exposed or critical systems. Validate actual configuration before assuming broad exposure. The critical score supports rapid patch governance, while the absence of documented exploitation reduces justification for emergency disruption without confirming applicability.
Technical view
TCP skb compaction can leave Linux kernel TLS parsing with a stale skb reference. tls_strp_check_rcv may then perform a slab use-after-free read while comparing queued records’ decryption state and geometry. The correction refreshes the receive queue before continuing.
Likely exposure
Exposure is limited to systems running a listed affected Linux release where the kernel TLS receive path is available and exercised. The bundle identifies 6.1, 6.1.147, 6.6.100, 6.12.40, 6.15.8, and 6.16, but does not clearly define complete affected ranges.
Exploitation context
The supplied record assigns CVSS 9.8, but provides only a KASAN-detected use-after-free read. It is not in KEV, and the bundle contains no evidence of active exploitation, a public proof of concept, or demonstrated remote code execution.
Researcher notes
The demonstrated condition is a stale skb dereference in tls_strp_check_rcv after aggressive TCP skb compaction. Available evidence establishes a slab use-after-free read, not reliable control of execution. Researchers should distinguish the CVSS impact assumptions from demonstrated outcomes and use the branch-specific stable commits when checking backports.
Mitigation direction
Install a vendor-supported kernel update containing the applicable upstream stable correction.
Review Debian, Siemens, or other relevant vendor advisories for product-specific fixed versions.
Prioritize internet-facing or high-availability systems that actively use kernel TLS.
If updates must wait, consult vendor guidance for supported temporary risk-reduction measures.
Validation and detection
Inventory running kernel versions and compare them with applicable vendor advisories.
Confirm the installed kernel includes the relevant stable correction for its release branch.
Determine whether kernel TLS receive functionality is enabled and used on each system.
After updating, verify the fixed kernel is running rather than merely installed.
Monitor kernel diagnostics for TLS-related KASAN reports, crashes, or abnormal receive-path behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38471 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.