CVE-2025-38471: Linux Kernel use-after-free (CVSS 9.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").

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Debian Linux11.0

Linux Kernel≥ 6.0.6 < 6.1 · ≥ 6.1.1 < 6.1.147 · ≥ 6.13 < 6.15.8 · ≥ 6.2 < 6.6.100

Remediation

Fixed in

Linux Kernel≥ 6.1

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-38471 being actively exploited?

CVE-2025-38471 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.41%.

How severe is CVE-2025-38471?

CVE-2025-38471 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.41% probability of exploitation.

Which products are affected by CVE-2025-38471?

Affected products include Debian Linux, Linux Kernel.

How do I fix CVE-2025-38471?

Upgrade affected software to a fixed version, for example Linux Kernel 6.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-38471 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo