CVE Tools

CVE-2025-39682

tls: fix handling of zero-length records on the rx_list

Exploited in the wild. In CISA KEV since 2026‑09‑18. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU, CSAF

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check every Linux server and appliance for its running kernel version and confirm with its operating-system vendor whether its installed security package includes CVE-2025-39682.
  2. Install the vendor-provided kernel security update; for the upstream 6.1 branch, update to 6.1.149 or later.
  3. Restart into the updated kernel and verify the running version after reboot.
  4. If an update cannot be applied immediately, follow your vendor's mitigation guidance and prioritize internet-facing systems.

What it is

From the CVE record

SIMATIC CN 4100 contains multiple vulnerabilities which could potentially lead to a compromise in availability, integrity and confidentiality. Siemens has released a new version for SIMATIC CN 4100 and recommends to update to the latest version.

In plain language

Written by AI from the record

This is a critical flaw in unpatched Linux kernel systems that attackers are already using, so small businesses running Linux servers should treat it as an emergency.

CVE-2025-39682 is a network-reachable Linux kernel TLS handling flaw involving zero-length records on the rx_list, with impacts to confidentiality, integrity, and availability.

If you're affected

  • Server takeover
  • Sensitive data exposure
  • Data tampering
  • Service outages
  • Ransomware risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS86th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2026-09-18.

US federal agencies must remediate by 2026-09-21.

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.
Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

2.9% chance of exploitation activity in the next 30 days, which ranks it in the 86th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained, driven by in-the-wild reports.

Lifecycle

A public exploit existed 67 days before the patch.

  1. Patch availablerecord updated
  2. Added to CISA KEVpatch available, patch available, record updated, record updated
  3. Patch availablerecord updated
  4. OpenVAS check added
  5. Patch availablerecord updated
  6. Public exploit / PoCsource: github-poc

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Debian GNU/Linux, not every advisory. This one: actively exploited.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store