CVE-2025-39682

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.

Severity
CRITICAL
CVSS v3
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · source cna
Exploit chance (EPSS)
3.312%
chance of exploitation in the next 30 days
higher than 88.8% of scored CVEs · 2026-11-17
CISA KEV
Listed
added 2026-09-18
Public exploit code
None public
Attackers are using this, but no public exploit code was found in these sources.
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA Known Exploited Vulnerabilities entry

Vulnerability nameLinux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability
Vendor / productLinux / Kernel
Date added2026-09-18
Federal remediation due date2026-09-21
Required actionApply 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.
Known ransomware campaign useUnknown

CISA SSVC decision points

Exploitationactive
Automatableyes
Technical impacttotal
Scored2026-09-19

Timeline

  1. 2025-09-05Published by the CNA17:20 UTC
  2. 2026-09-18Added to the CISA KEV catalog378 days after publication
  3. 2026-09-19CISA SSVC decision recorded379 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
linux linux_kernelfrom 6.0 before 6.1.149fixed in 6.1.149from 6.0 before 6.12.44fixed in 6.12.44from 6.7 before 6.12.44fixed in 6.12.44from 6.0 before 6.16.4fixed in 6.16.4from 6.13 before 6.16.4fixed in 6.16.4(+4 more)6.1.1496.12.446.12.446.16.46.16.4
debian debian_linux11.0no fix listednot listed
siemens simatic_cn_4100_firmwarebefore 5.0fixed in 5.05.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources