CISA list

As of , CVE-2025-39682 in Linux Kernel is on CISA's list of exploited vulnerabilities: CISA listed it on . Our patch-first group: Patch now.

CVE-2025-39682

Linux Kernel: Improper Check for Unusual or Exceptional Conditions. Exploited, and in our Patch now group.

Our patch-first group

Patch now

  • Forensic triage required by CISA

CISA's required action

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.

Patch infofixed versions and vendor advice

What to install

  • Affects Linux. The record gives its versions in a form this page does not read.

Vendor advice

Vendor advice: git.kernel.org, from CISA's entry.

EPSS score
0.03
Higher than 88% of the CVEs EPSS scores.

EPSS estimates the chance of exploitation activity in the next 30 days.

Exploited
Yes CISA listed it on 18 September 2026
US federal deadline
21 September 2026 3 days after CISA listed it. US federal civilian agencies must fix it by then.
Used in ransomware campaigns
Not known to CISA
EPSS when listed
0.01 on 18 September 2026 EPSS on the day CISA listed it.
Public exploit
None found Neither Metasploit nor Exploit-DB lists one.

Since listing

EPSS since listing

0.000.501.000.50: EPSS line for Patch this weekListed by CISA1 Oct1 Nov0.000.501.00Listed by CISA1 Oct1 Nov

EPSS for CVE-2025-39682 since CISA listed it, on the days its value to 2 decimals changed. EPSS scores by FIRST.

Show the numbers
FromEPSS
0.01
0.02
0.03

Timeline

What happened when

  1. The CVE record was published.
  2. CISA added it to its list of exploited vulnerabilities.
  3. The US federal deadline to fix it.

CISA's required action

What CISA says to do

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.

Agencies must also look for signs that attackers already got in.

Read further: CISA's catalog

The flaw

What the flaw is

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.

CISA's description

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.

The CVE record's description, from Linux

CVE published
5 September 2025
Assigned by
Linux
CVSS
9.8 Critical (CVSS 3.1, from the CNA)
CWE-754
Improper Check for Unusual or Exceptional Conditions
CISA SSVC, exploitation
active
CISA SSVC, automatable
yes
CISA SSVC, technical impact
total

Same product

Kernel: other exploited entries

All 32 entries for Kernel
Other exploited Kernel entries
VulnerabilityProductOur groupListedDeadlineEPSS
CVE-2026-46300Missing Initialization of a VariableKernelPatch nowCISA triageMetasploitDue0.17
CVE-2022-0995Out-of-Bounds WriteKernelPatch nowCISA triageMetasploitDue0.09
CVE-2025-39964Race ConditionKernelPatch nowCISA triageDue0.02
CVE-2026-53362UnspecifiedKernelPatch nowCISA triageDue0.01
CVE-2026-53266Out-of-Bounds WriteKernelPatch nowCISA triageDue0.01
CVE-2021-22555Heap Out-of-Bounds WriteKernelPatch this weekMetasploitExploit-DBDue0.79
CVE-2013-6282Improper Input ValidationKernelPatch this weekMetasploitExploit-DBDue0.40
CVE-2019-13272Improper Privilege ManagementKernelPatch this weekMetasploitExploit-DBDue0.52
CVE-2010-3904Improper Input ValidationKernelPatch this weekMetasploitExploit-DBDue0.16
CVE-2026-31431Incorrect Resource Transfer Between SpheresKernelPatch this weekMetasploitDue0.98
Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • CWE names: Copyright © 2006-2026, The MITRE Corporation. CWE, CWSS, CWRAF, and the CWE logo are trademarks of The MITRE Corporation (source). Licence: CWE Terms of Use
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)