CVE-2025-39682: critical vulnerability in Linux
tls: fix handling of zero-length records on the rx_list
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
Prioritize patching. It under exploitation confirmed by CISA, has an official Brazilian government alert and has a public proof of concept.
Brazil's federal government published an alert, recommendation or bulletin that cites this vulnerability.
- CISC Gov.br · 24 Sep 2026Boletim do CISC de Vulnerabilidadesread on gov.br ↗
Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.
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.
The Linux kernel's TLS implementation fails to properly handle zero-length records that come from an internal queue (rx_list), potentially causing memory corruption or denial of service. This flaw affects systems using TLS encryption, particularly with TLS 1.3 where record types are only known after decryption.
A zero-length TLS record retrieved from the rx_list after zero-copy decryption can bypass proper state validation, as the kernel assumes zero-copy operations only occur with data records. An attacker able to influence TLS record processing (network-level or via malicious TLS server) can trigger this path, potentially leading to memory safety violations or crashes in the kernel's TLS stack.
In the same product, most dangerous first.