Linux Kernel: Exploited Flaw CVE-2025-39682
Published October 25, 2026 · Last updated October 25, 2026
Linux Linux Kernel CVE KEV Critical Patch
What happened: On September 18, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2025-39682, a flaw in Linux Kernel, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability."
CISA's summary: "Linux Kernel contains an improper check for unusual or exceptional conditions vulnerability in the TLS receive path which allows a zero-length record retrieved from the rx_list to bypass the intended recvmsg() record-type handling, potentially causing subsequent TLS records to be processed using incorrect zero-copy and queuing assumptions. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version."
What the National Vulnerability Database says
NVD first published CVE-2025-39682 on September 5, 2025. Its description, from the record's source (416baaa9-dc9f-4396-8d5f-8c081fb06d67), reads: "In the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length."
How serious is CVE-2025-39682?
The CVSS 3.1 base score is 9.8 out of 10 (Critical), scored by nist.gov. In plain terms: an attacker can reach the Kernel weakness over a network, including the internet; the attacker does not need an account; no one has to click or open anything. The listed impact on Kernel data secrecy is high, on data integrity high, and on availability high. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Which Kernel versions are affected?
The CVE record lists these affected ranges:
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 up to, but not including, 2902c3ebcca52ca845c03182000e8d71d3a5196f
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 up to, but not including, c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 up to, but not including, 3439c15ae91a517cf3c650ea15a8987699416ad9
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 up to, but not including, 29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e
- 84c61fe1a75b4255df1e1e7c054c9e6d048da417 up to, but not including, 62708b9452f8eb77513115b17c4f8d1a22ebf843
- version 6.0
- versions before V5.0
If your Kernel version falls in one of these ranges, check Linux's advisory for the fixed release that applies to you.
What kind of weakness is it?
CISA and NVD map CVE-2025-39682 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):
- CWE-754: Improper Check for Unusual or Exceptional Conditions. MITRE's definition: "The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product."
CISA required action for CVE-2025-39682
CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines."
Timeline for CVE-2025-39682
- October 19, 2026: latest change to the NVD record (status: Analyzed).
- September 18, 2026: CISA adds CVE-2025-39682 to the KEV catalog.
- September 21, 2026: due date for U.S. federal civilian agencies to act on CVE-2025-39682.
- September 5, 2025: NVD publishes CVE-2025-39682.
Other scores in the NVD record: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 scores it 9.8 (Critical) under CVSS 3.1.
Advisories and technical references
The NVD record for CVE-2025-39682 links to these references; tags in brackets are NVD's labels:
- git.kernel.org/stable/c/2902c3ebcca52ca845c03182000e8d71d3a5196f (Patch)
- git.kernel.org/stable/c/29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e (Patch)
- git.kernel.org/stable/c/3439c15ae91a517cf3c650ea15a8987699416ad9 (Patch)
- git.kernel.org/stable/c/62708b9452f8eb77513115b17c4f8d1a22ebf843 (Patch)
- git.kernel.org/stable/c/c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677 (Patch)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (Mailing List, Third Party Advisory)
- cert-portal.siemens.com/productcert/html/ssa-032379.html (Third Party Advisory)
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-39682 (US Government Resource)
What to do
- Run Linux Kernel? Follow Linux's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
- Federal civilian agencies must act by September 21, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for Kernel too.
- Ransomware use: CISA lists known ransomware campaign use for CVE-2025-39682 as "Unknown".
- Don't run Kernel yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2025-39682" and asks for payment or remote access, that is a scam pattern, not a Linux alert.
CVE-2025-39682 record details from CISA and NVD
- CISA forensic triage flag for CVE-2025-39682: Yes
- Attack complexity for CVE-2025-39682: low
- CVE-2025-39682 CVSS scope: unchanged
- NVD sub-scores for CVE-2025-39682: exploitability 3.9, impact 5.9.
- Who mapped the weakness type: 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary); [email removed] (Primary)
- NVD product identifiers (CPE):
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*,cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*,cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*,cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*,cpe:2.3:o:siemens:simatic_cn_4100_firmware:*:*:*:*:*:*:*:* - References in the NVD record: 8 (5 tagged Patch, 2 tagged Third Party Advisory, 1 tagged Mailing List).
- CISA SSVC decision points for CVE-2025-39682 (from NVD): exploitation=active; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Sources
- CISA KEV Catalog: CVE-2025-39682
- NVD: CVE-2025-39682
- Linux advisory
- Linux advisory
- Linux advisory
- MITRE CWE-754
General education only, not security advice. Facts checked against the sources above on the date shown.