CVE-2025-39682
Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability
Description
CVE-2025-39682 is a critical flaw in the Linux kernel's kTLS receive path: tls_sw mishandles zero-length records on the rx_list. Each recvmsg() call must process either a run of contiguous DATA records or a single non-DATA record, and when a record has already been decrypted it is queued to the rx_list for the next call. Zero-copy decryption writes straight into the user space buffer and leaves no skb to queue — which is safe only because zero-copy applies to data records alone. The corner case the kernel missed is an initial record taken from the rx_list that is zero length. Affected are kernels 6.0 up to 6.1.149, 6.2 up to 6.6.103, 6.7 up to 6.12.44, 6.13 up to 6.16.4 and 6.17, along with Debian 11 and Siemens SIMATIC CN 4100 firmware below 5.0. CISA has added CVE-2025-39682 to the Known Exploited Vulnerabilities catalog, and its remediation deadline of September 21, 2026 has already passed.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CalculatorCWEs
Affected Products
| Vendor | Product | Version |
|---|---|---|
| linux | linux kernel | >= 6.0, < 6.1.149; >= 6.2, < 6.6.103; >= 6.7, < 6.12.44; >= 6.13, < 6.16.4; 6.17 |
| debian | debian linux | 11.0 |
| siemens | simatic cn 4100 firmware | < 5.0 |
Multiple CVSS Assessments
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References
- https://git.kernel.org/stable/c/2902c3ebcca52ca845c03182000e8d71d3a5196f(Patch)
- https://git.kernel.org/stable/c/29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e(Patch)
- https://git.kernel.org/stable/c/3439c15ae91a517cf3c650ea15a8987699416ad9(Patch)
- https://git.kernel.org/stable/c/62708b9452f8eb77513115b17c4f8d1a22ebf843(Patch)
- https://git.kernel.org/stable/c/c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677(Patch)
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html(Mailing List, Third Party Advisory)
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html(Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-39682(US Government Resource)
Weakness Type
CWE-754: Improper Check for Unusual or Exceptional Conditions
This weakness arises when software fails to check for a condition that is not expected to occur in normal operation — an edge case, an unusual input, an error return — and therefore continues in an invalid state. In the kernel's TLS receive handling, the ordinary paths are sound: zero-copy is restricted to data records, and the loop breaks after each non-data record, so the combination of zero-copy and a changed record type should be impossible. The unchecked exceptional condition is the one case that escapes that reasoning, an initial zero-length record coming from the rx_list.
Learn more: CWE-754 — Improper Check for Unusual or Exceptional Conditions
Impact Analysis
CVE-2025-39682 has a CVSS 3.1 base score of 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Attack Vector (Network), Privileges Required (None), User Interaction (None), Attack Complexity (Low): the trigger arrives in the TLS record stream itself, so a peer — or anyone able to inject into the connection — reaches the flawed path without credentials on the target and without anyone's cooperation. Confidentiality, Integrity and Availability (all High): the defect sits in kernel code handling a user space buffer, and a mismatch between what was decrypted and where it was written is the kind of state confusion that yields memory disclosure or corruption in the most privileged context on the machine. The exposure depends on kTLS actually being in use, which is the significant scoping consideration: kernel TLS is enabled by high-throughput TLS terminators, CDNs, proxies and storage protocols rather than by every Linux host, but those are precisely the systems that terminate large numbers of untrusted connections. The EPSS score of 2.9% in the 87th percentile is high for a kernel issue, and CISA has confirmed exploitation in the wild.
Exploit Maturity
CISA has added CVE-2025-39682 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 21, 2026 has already passed; the entry does not flag use in ransomware campaigns. The references are the upstream stable commits, the Debian LTS announcement and Siemens advisory SSA-032379 — patches rather than exploit code, so no public proof-of-concept is listed. For kernel vulnerabilities the patch itself is informative, however: the commit message describes the corner case precisely, which is standard practice upstream and gives a researcher a clear starting point. The EPSS score of 2.9% places this in the 87th percentile, high for a Linux kernel CVE, where the great majority score far lower. Combined with the KEV listing, the realistic assessment is that a working exploit exists for the kTLS configuration and that hosts terminating TLS in the kernel are the population at risk.
Remediation
- Carry out the action CISA requires, immediately. Apply mitigations in accordance with your kernel vendor's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of September 21, 2026 has already passed.
- Update the kernel to a fixed stable release — 6.1.149, 6.6.103, 6.12.44 or 6.16.4 and later in their respective series — or install your distribution's patched kernel package. The upstream fixes are published as stable commits, among them 2902c3ebcca5 and 3439c15ae91a; Debian covered it in its LTS announcement. A kernel update requires a reboot or live patching to take effect — an installed package alone does not fix a running system.
- Determine whether kTLS is actually in use. The flaw is in the kernel TLS software receive path, so hosts that do not enable kTLS are not exposed through it. Check for the
tlsmodule and for applications configured to offload TLS to the kernel (high-performance web servers, proxies and some storage stacks), and prioritize those systems — but still patch the rest on the normal schedule. - Do not forget embedded and appliance kernels. The affected list includes Siemens SIMATIC CN 4100 firmware below 5.0, covered by Siemens advisory SSA-032379, and Debian 11. Devices that embed a Linux kernel need their vendor's firmware update, and they are the installations most likely to be missed.
- Reduce what a kernel compromise reaches. Keep TLS-terminating hosts in their own network segment with minimal onward trust, run workloads in separate privilege domains so that a single host does not hold the credentials of the whole estate, and enable kernel hardening and live patching infrastructure so that the next kernel flaw can be closed without a maintenance window.
Technical Details
In the kernel's software kTLS receive path, recvmsg() must process either any number of contiguous DATA records or exactly one non-DATA record; when the next record differs in type the loop breaks, and if that record has already been decrypted — which happens with TLS 1.3, where the type is only known after decryption — it is queued to the rx_list for the following call. Queuing is impossible after a zero-copy decrypt, because the plaintext went straight into the user space buffer and darg.skb points at the ciphertext skb kept only for metadata such as length. The design argument for safety is that zero-copy applies only to data records and the loop breaks after every non-data record, so the combination cannot arise. The missed corner case is an initial record that comes from the rx_list and is zero length; the exceptional condition is not checked, and the code proceeds in a state it was never meant to reach — CWE-754. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H reflects a remotely reachable, unauthenticated path with complete impact; the scope is marked unchanged even though the affected component is the kernel itself.
Frequently Asked Questions
Is CVE-2025-39682 being actively exploited?
Yes. CISA has added CVE-2025-39682 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 21, 2026 has already passed. Use in ransomware campaigns is not recorded, and the EPSS score of 2.9% places the vulnerability in the 87th percentile — unusually high for a Linux kernel issue.
What products are affected by CVE-2025-39682?
CVE-2025-39682 affects the Linux kernel from 6.0 up to 6.1.149, from 6.2 up to 6.6.103, from 6.7 up to 6.12.44, from 6.13 up to 6.16.4, and version 6.17. Debian 11 and Siemens SIMATIC CN 4100 firmware below 5.0 are listed as affected products as well, each addressed by its own vendor update. Exposure in practice requires kernel TLS to be in use.
How do I fix CVE-2025-39682?
Update to a fixed stable kernel — 6.1.149, 6.6.103, 6.12.44 or 6.16.4 and later — or install your distribution's patched kernel package, then reboot or apply live patching, since an installed package does not fix a running kernel. Appliances and embedded systems need their vendor's firmware update, such as the Siemens fix for SIMATIC CN 4100 below version 5.0.
How severe is CVE-2025-39682?
CVE-2025-39682 is rated Critical with a CVSS 3.1 base score of 9.8: remotely reachable through the TLS record stream, unauthenticated, no user interaction, with full impact on confidentiality, integrity and availability in kernel context. Its EPSS score of 2.9% is in the 87th percentile. The practical severity depends on whether a host uses kernel TLS — but on the high-throughput TLS terminators that do, it is as serious as the rating implies.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.