# CVE-2025-38471: tls: always refresh the queue when reading sock > A use-after-free bug in the Linux kernel TLS module allows attackers to cause a system crash or potentially execute arbitrary code. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Jul 2025 - **Updated:** 15 Oct 2026 - **Also known as:** AZL-65949, BELL-CVE-2025-38471, DEBIAN-CVE-2025-38471, GHSA-8r96-vh27-xgf4, RHSA-2025:14497, RHSA-2025:14599, RHSA-2025:14811, ROOT-OS-DEBIAN-12-CVE-2025-38471, ROOT-OS-UBUNTU-2404-CVE-2025-38471, UBUNTU-CVE-2025-38471 ## What is CVE-2025-38471? CVE-2025-38471 is a critical use after free vulnerability in Debian Debian Linux, published on 28 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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"). Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2025-38471? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kpatch-patch-5_14_0-570_17_1` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-6.el9_6 | | `kpatch-patch-5_14_0-570_17_1-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-6.el9_6 | | `kpatch-patch-5_14_0-570_17_1-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-6.el9_6 | | `kpatch-patch-5_14_0-284_104_1` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-6.el9_2 | | `kpatch-patch-5_14_0-284_104_1-debuginfo` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-6.el9_2 | | `kpatch-patch-5_14_0-284_104_1-debugsource` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-6.el9_2 | | `kpatch-patch-5_14_0-284_117_1` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-3.el9_2 | | `kpatch-patch-5_14_0-284_117_1-debuginfo` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-3.el9_2 | | `kpatch-patch-5_14_0-284_117_1-debugsource` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-3.el9_2 | | `kpatch-patch-5_14_0-284_52_1` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-14.el9_2 | | `kpatch-patch-5_14_0-284_52_1-debuginfo` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-14.el9_2 | | `kpatch-patch-5_14_0-284_52_1-debugsource` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-14.el9_2 | | `kpatch-patch-5_14_0-284_79_1` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-10.el9_2 | | `kpatch-patch-5_14_0-284_79_1-debuginfo` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-10.el9_2 | | `kpatch-patch-5_14_0-284_79_1-debugsource` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-10.el9_2 | | `kpatch-patch-5_14_0-284_92_1` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-8.el9_2 | | `kpatch-patch-5_14_0-284_92_1-debuginfo` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-8.el9_2 | | `kpatch-patch-5_14_0-284_92_1-debugsource` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1-8.el9_2 | | `kpatch-patch-5_14_0-427_13_1` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-12.el9_4 | | `kpatch-patch-5_14_0-427_13_1-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-12.el9_4 | | `kpatch-patch-5_14_0-427_13_1-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-12.el9_4 | | `kpatch-patch-5_14_0-427_31_1` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-10.el9_4 | | `kpatch-patch-5_14_0-427_31_1-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-10.el9_4 | | `kpatch-patch-5_14_0-427_31_1-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-10.el9_4 | | `kpatch-patch-5_14_0-427_44_1` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-8.el9_4 | | `kpatch-patch-5_14_0-427_44_1-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-8.el9_4 | | `kpatch-patch-5_14_0-427_44_1-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-8.el9_4 | | `kpatch-patch-5_14_0-427_55_1` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-6.el9_4 | | `kpatch-patch-5_14_0-427_55_1-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-6.el9_4 | | `kpatch-patch-5_14_0-427_55_1-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-6.el9_4 | | `kpatch-patch-5_14_0-427_68_2` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-3.el9_4 | | `kpatch-patch-5_14_0-427_68_2-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-3.el9_4 | | `kpatch-patch-5_14_0-427_68_2-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1-3.el9_4 | Products: Debian Debian Linux, Linux kernel. ## How do I fix CVE-2025-38471? Apply the vendor's patch. ## Is CVE-2025-38471 being exploited? There is no known exploitation of CVE-2025-38471 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-38471 and fix it if it is affected. What it is: CVE-2025-38471 is a critical use after free vulnerability in Debian Debian Linux, published on 28 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-38471 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-38471/ (Markdown: https://insights.sbomify.com/CVE-2025-38471/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-38471 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-38471 - OSV: https://osv.dev/vulnerability/CVE-2025-38471 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-38471/ Summaries are generated and may contain mistakes; the official description above is the record.