Advisory

CVE-2025-39682 (CVSS 9.8 Critical): Linux Kernel TLS Zero-Length Record Flaw — Patch Now

A critical vulnerability in the Linux kernel's TLS receive path allows a zero-length record retrieved from an internal queue to bypass intended record-type handling, potentially enabling unauthenticated remote attackers to compromise confidentiality, integrity, and availability. The flaw is listed in the CISA Known Exploited Vulnerabilities catalog, making prompt remediation urgent.

TL;DR: Apply available Linux kernel patches addressing CVE-2025-39682 immediately, or discontinue use of affected end-of-life kernel versions per CISA guidance. Verify that any internet-exposed systems using kernel TLS are updated.

What Is the Vulnerability?

CVE-2025-39682 is a Critical vulnerability (CVSS 3.1 score: 9.8, vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in the Linux kernel's in-kernel TLS (kTLS) implementation, specifically in how the recvmsg() path handles records queued on the rx_list.

The kernel's TLS receive logic enforces a strict rule per recvmsg() call:

  • Process any number of contiguous DATA records, or
  • Process exactly one non-DATA record.

When record types differ mid-loop, the kernel breaks out and queues the pending record onto the rx_list for the next recvmsg() call. For TLS 1.3, the actual record type is not known until after decryption, which makes this queuing path particularly important.

The flaw — classified as CWE-754 (Improper Check for Unusual or Exceptional Conditions) — occurs when the first record in a recvmsg() call comes from the rx_list and has zero length. This edge case was not handled correctly, causing the subsequent TLS record processing to operate under incorrect zero-copy and queuing assumptions — assumptions that only hold for DATA records processed normally, not for records originating from the queue at zero length.

Specifically, zero-copy decryption writes directly to user-space buffers, so there is no kernel-side socket buffer (skb) to re-queue if the record type changes unexpectedly. When a zero-length rx_list record triggers this code path, the safeguards that prevent type confusion break down.

Who and What Is Affected?

The vulnerability resides in the Linux kernel, produced by the Linux kernel community. Any system running an affected kernel version that has kTLS enabled in its network stack may be vulnerable. This includes:

  • Linux distributions shipping affected kernel versions (server, desktop, container host, and embedded configurations alike)
  • Systems where applications delegate TLS handling to the kernel via the SOL_TLS socket option
  • TLS 1.3 connections, which are particularly implicated because record type is determined post-decryption

CISA notes that the impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users running EoL kernel versions should treat this with extra urgency, as vendor-supplied patches may not be forthcoming for older branches.

The CVSS vector indicates: no authentication required, no user interaction required, network-reachable — meaning exploitation does not require an attacker to hold any credentials or trick a user into performing an action.

What Is the Potential Impact?

The CVSS base score of 9.8 (Critical) reflects the highest possible ratings across confidentiality, integrity, and availability:

  • Confidentiality (High): An attacker may be able to read TLS-protected data that should have been isolated, potentially exposing sensitive application data traversing encrypted connections.
  • Integrity (High): Incorrect processing assumptions could allow manipulation of TLS record handling, potentially corrupting or forging data in the receive path.
  • Availability (High): Triggering the flawed condition could cause kernel-level instability, crashes, or denial of service on affected hosts.

Because this vulnerability exists at the kernel level, successful exploitation could affect all processes and connections on the host — not just a single application. Network-facing systems that offload TLS to the kernel are exposed over the network without any prerequisite access or interaction from the victim side.

CISA has added this vulnerability to the Known Exploited Vulnerabilities (KEV) catalog (added: 2026-09-18), indicating that exploitation has been observed. Federal agencies subject to CISA's Binding Operational Directive 26-04 have mandatory remediation timelines; all organizations should treat this as high priority regardless.

What Should You Do Now?

CISA's required action for this KEV entry is clear: apply mitigations per vendor instructions, follow BOD 26-04 patching guidelines based on internet exposure, and — if the product is EoL and mitigations are unavailable — discontinue use or transition to a supported version.

  1. Identify affected kernel versions: Audit all systems running Linux kernels with kTLS support. Determine which kernel versions are deployed and whether patches addressing CVE-2025-39682 are available for those versions from your distribution vendor.
  2. Apply kernel patches: Install the patched kernel version as provided by your Linux distribution (e.g., via your distribution's package manager or vendor security portal). The upstream fix addresses the zero-length rx_list record edge case in the TLS receive path.
  3. Prioritize internet-exposed systems: Systems where kTLS-enabled services are reachable from untrusted networks carry the highest risk. Address these first in accordance with CISA BOD 26-04 guidance.
  4. Migrate off EoL kernels: If running an end-of-life kernel version for which no patch is available, plan and execute migration to a supported kernel branch promptly. Running EoL kernels in production, especially on internet-facing hosts, is not advisable.
  5. Reboot after patching: Linux kernel patches require a system reboot (or live-patching tooling where available) to take effect. Confirm the new kernel is active post-patch.
  6. Consult primary sources: Monitor the NVD entry for CVE-2025-39682 and the CISA KEV catalog for updated guidance and patch references.

How External Security Testing Can Surface This Exposure

External security assessments can help organizations understand their exposure to CVE-2025-39682 before or after remediation:

  • Version fingerprinting: Network and host-based scanning can identify kernel versions running on exposed systems. Knowing which kernel version is active is the first step in determining whether a host is unpatched and vulnerable.
  • Service enumeration: Identifying which network services have kTLS offloading enabled helps scope the actual attack surface. Not all Linux systems expose kTLS-using services to the network.
  • Configuration review: Point-in-time assessments can verify whether TLS-offloading is in use, whether affected kernel versions are deployed, and whether patch application has been confirmed — supporting prioritization decisions for patching queues.
  • Internet exposure mapping: Determining which hosts running affected kernels are directly reachable from the internet allows teams to triage remediation order in line with CISA BOD 26-04's risk-based patching guidance.

Because this is a kernel-level vulnerability affecting a core networking subsystem, accurate inventory and version tracking across your fleet is essential — gaps in asset visibility directly translate to unpatched exposure.

Sources & further reading: NVD CVE-2025-39682 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: git.kernel.org, git.kernel.org, git.kernel.org, git.kernel.org. This advisory contains no exploit code.

Frequently asked questions

Is CVE-2025-39682 being actively exploited?

Yes. CISA added CVE-2025-39682 to its Known Exploited Vulnerabilities (KEV) catalog on 2026-09-18, indicating that exploitation has been observed in the wild. All organizations — not just federal agencies — should treat this as an urgent remediation priority.

Do I need to have kTLS explicitly configured to be vulnerable?

The vulnerability is in the Linux kernel's in-kernel TLS (kTLS) receive path, which is exercised when applications or network services use the kernel's TLS offloading feature via the SOL_TLS socket option. If your systems do not use kTLS, the specific code path may not be reachable; however, patching the kernel is still the correct course of action regardless, as the patch resolves the flaw definitively.

What if I am running an end-of-life kernel version and no patch is available?

CISA explicitly notes that affected products could be end-of-life or end-of-service, and advises users to discontinue use and transition to a supported version if mitigations are unavailable. Running an EoL kernel on an internet-exposed host with this vulnerability present carries significant risk. Migration to a currently maintained kernel branch is the recommended path.

Where can I find the official patch and further guidance?

Consult your Linux distribution's security advisory channel (such as your distribution's security mailing list or errata portal) for the specific patched kernel package. For authoritative vulnerability details, refer to the NVD entry at nvd.nist.gov for CVE-2025-39682, and to the CISA KEV catalog at cisa.gov/known-exploited-vulnerabilities-catalog for required action guidance.