CVE-2025-39682

criticalpriority · act · 90OT risk · criticalKEV · exploitedEPSS 0.029 · 87 %ileexploit · PoCDEEUNLRUUS
grimoire priorityP0 · Act now
Exploitable?
Yes · in the wild
CISA KEV · 2 exploits · PoC
Likely / severe?
2.88% (87th) EPSS
CVSS 9.8 · critical
Is it mine?
112 products
Check your exposure
Who says so?
9 sources
cnnvd · enisa_euvd · fstec_bdu · osv

added 2026-09-18remediate by 2026-09-21

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.

EPSS · scored 2026-10-22

Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability

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.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • FixedSIMATIC CN 4100siemens_psirt

    Update to V5.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814144/
  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.ppc64le as component of SUSE Linux Enterprise Server 16.0suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.ppc64le as component of SUSE Linux Enterprise Server for SAP applications 16.0suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.s390x as component of SUSE Linux Enterprise Server 16.0suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.s390x as component of SUSE Linux Enterprise Server for SAP applications 16.0suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.x86_64 as component of SUSE Linux Enterprise Server 16.0suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.x86_64 as component of SUSE Linux Enterprise Server for SAP applications 16.0suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.ppc64le as component of SUSE Linux Micro 6.2suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.s390x as component of SUSE Linux Micro 6.2suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • Fixedkernel-livepatch-6_12_0-160000_5-default-0:5-160000.4.3.x86_64 as component of SUSE Linux Micro 6.2suse_csaf

    To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

  • FixedSIMATIC CN 4100cisa_csaf_ot

    Update to V5.0 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814144/
02

cvss

Technical severity, 0–10. One row per scoring source.

9.8
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7–9.8

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hprimary · NVD / NIST USexploitability 3.9 · impact 5.9
v3.17highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:Hsecondary · CISA US
v3.17highAV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:Hsecondary · FSTEC (BDU) RU
v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · ENISA EU
v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondaryexploitability 3.9 · impact 5.9
v3.17highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:Hsecondary · Siemens ProductCERT DE
v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:Hsecondary · CVSS-BT (t0sche)
v3.17highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:Hsecondary · SUSE Product Security
v3.17.1highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Hsecondary · NCSC-NL NL
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: active · Automatable: yes · Technical Impact: totalcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-120USCWE-20USCWE-20USCWE-754US
05

exploits (2)

Public proof-of-concept and weaponised exploit code.

06

affected products (112)

Products and version ranges known to be affected.

showing 20 of 112
07

advisories (9)

Vendor and ecosystem advisories describing this.

  • NCSC-2026-0074Kwetsbaarheden verholpen in Google Android en Samsung MobileNL2026-03-03csaf · ncsc_nlNL

    Google heeft kwetsbaarheden verholpen in Android. In deze update zijn ook updates meegenomen voor closed-source componenten van Qualcomm, Imagination Technologies, Unisoc en MediaTek. Samsung heeft kwetsbaarheden in Samsung Mobile verholpen die relevant zijn voor Samsung mobile devices.

  • NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-productenNL2026-05-13csaf · ncsc_nlNL

    Siemens heeft kwetsbaarheden verholpen in verschillende (OT-)producten. Het gaat onder andere om producten in de Siemens RUGGEDCOM-, SCALANCE-, SIMATIC-, SIMIT-, SINAMICS-, SIPROTEC-, SENTRON- en Solid Edge-productreeksen.

  • SSA-032379SSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.02026-05-12csaf · siemens_psirtDE

    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.

  • SUSE-SU-2026:20149-1Security update for the Linux Kernel (Live Patch 0 for SUSE Linux Enterprise 16)2026-01-26csaf · suse_csafDE

    Security update for the Linux Kernel (Live Patch 0 for SUSE Linux Enterprise 16)

  • SUSE-SU-2026:20169-1Security update for the Linux Kernel (Live Patch 0 for SUSE Linux Enterprise 16)2026-01-26csaf · suse_csafDE

    Security update for the Linux Kernel (Live Patch 0 for SUSE Linux Enterprise 16)

  • WID-SEC-W-2025-1988Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of ServiceDeutsch2025-09-07csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.

  • WID-SEC-W-2026-0569Google Android: Mehrere SchwachstellenDeutsch2026-03-02csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um sich erweiterte Berechtigungen zu verschaffen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu verursachen, vertrauliche Informationen offenzulegen oder andere nicht näher spezifizierte Angriffe durchzuführen.

  • ICSA-26-134-10Siemens SIMATIC2026-05-12icsa · cisa_csaf_otUS

    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.

  • ASB-A-4405445112026-03-01vendor · osvUS

    In tls_sw_recvmsg of tls_sw.c, there is a possible use after free due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

08

also known as (10)

Other names and identifiers for this entity.

09

sources

Which sources assert this record, and when.

cnnvdenisa_euvdfstec_bduosvcert_bundncsc_nlsiemens_psirtsuse_csafcisa_csaf_otNVDCVE.orgMITRE
published 2025-09-05modified 2026-10-19
10

references (19)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan