Skip to content
NewA calmer, faster ZeroHour
VulnerabilityKEV3 · 1 read

CVE-2025-39682

Improper Condition Check in Linux Kernel kTLS Receive Path Enables Local Info Leak/DoS

CISA: Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability

CVSS 3.1
9.8 critical
EPSS
3%p88
Published
·
Added to KEV
Analyze CVE-2025-39682 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

The Linux kernel's in-kernel TLS (kTLS) implementation mishandles zero-length records on the rx_list: each recvmsg() call must process either contiguous DATA records or a single non-DATA record, and the missed corner case occurs when the initial record is pulled from the rx_list and is zero length, breaking the check on record-type changes after zero-copy decryption. A local, low-privileged attacker able to use kTLS sockets can trigger this flaw, and the CVSS vector indicates high confidentiality impact (kernel information disclosure) and high availability impact (crash/DoS), with no integrity impact. Any Linux deployment running a kernel with the TLS (kTLS) feature enabled is affected, including Debian systems, which are listed as affected vendors in CISA's data. CISA added this vulnerability to the Known Exploited Vulnerabilities catalog on 2026-09-18, indicating known exploitation in the wild, though no public proof-of-concept is known and ransomware use is unconfirmed.

What to do: Update the Linux kernel to a release containing the upstream fix for this kTLS rx_list issue, applying Debian security updates where applicable, consistent with CISA BOD 26-04 patching guidance. As an interim mitigation, check whether kernel TLS is active (e.g., 'lsmod | grep tls' or CONFIG_TLS in the running kernel) and unload/disable the tls module on hosts that do not require kTLS. Limit local unprivileged access on multi-user systems, since exploitation requires a local low-privileged user.

ProductAffected
Linux Kernel—
Debian Linux—
Estimated exposure
mass≈100M+ systems potentially exposed (Linux kernel ubiquitous; only hosts with the kTLS module enabled and in use are vulnerable) — The Linux kernel runs on the majority of servers, cloud instances, and hundreds of millions of embedded devices, but the flaw is locally exploitable (AV:L/PR:L) and only reachable where kernel TLS (CONFIG_TLS/tls module) is loaded and used.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

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.

KEVCISA Known Exploited Vulnerability
Affected
Linux Kernel
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.
Due date
Ransomware use
Unknown
Vendors
linuxdebiansiemens
Products
linux kernel, debian linux, simatic cn 4100 firmware
Weakness
CWE-754
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

In the news

7 stories