Security Resilience

CVE-2025-39682

Linux Kernel 6.0 – 6.1.149

CISA KEVActive ExploitationEUVD Exploited
Published
05 September 2025
Modified
19 October 2026
KEV Added
18 September 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.033 88th percentile
Risk Priority 97 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-39682 is a critical-severity Improper Check for Unusual or Exceptional Conditions (CWE-754) vulnerability in Linux Kernel. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 12% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
KEV Date Added
18 September 2026

Related Threats

CVEs Like This One

CVE-2024-36971Same product: Debian Debian Linuxboth on KEV
CVE-2024-42160Same product: Debian Debian Linux
CVE-2024-35785Same product: Debian Debian Linux
CVE-2023-0266Same product: Debian Debian Linuxboth on KEV
CVE-2024-42159Same product: Debian Debian Linux
CVE-2024-53104Same product: Debian Debian Linuxboth on KEV
CVE-2025-38334Same product: Debian Debian Linux
CVE-2021-0920Same product: Debian Debian Linuxboth on KEV
CVE-2023-41993Same product: Debian Debian Linuxboth on KEV
CVE-2022-30333Same product: Debian Debian Linuxboth on KEV

Affected Assets

linux
linux kernel
6.17 · 6.0 — 6.1.149 · 6.2 — 6.6.103 · 6.7 — 6.12.44
debian
debian linux
11.0
siemens
simatic cn 4100 firmware
≤ 5.0

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-754

Requires detection and response to audit logging failures as an unusual or exceptional condition.

addresses: CWE-754

Implements detection of unusual or exceptional conditions followed by safe mode entry, reducing the window for exploitation of unchecked conditions.

addresses: CWE-754

Training ensures users perform required checks for unusual or exceptional conditions as part of contingency roles, limiting attacker leverage from skipped validations.

addresses: CWE-754

IR testing directly validates checks for unusual or exceptional conditions that could indicate security incidents.

addresses: CWE-754

Requires ongoing monitoring of organization-defined metrics and analysis, enabling checks for unusual or exceptional conditions.

addresses: CWE-754

Security testing routinely checks for unusual or exceptional inputs/conditions, identifying missing validation steps that flaw remediation then resolves.

addresses: CWE-754

Requires detection of unusual conditions followed by a controlled transition to the defined failure state.

addresses: CWE-754

MTTF determination forces explicit checks for conditions that precede predictable component failure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance verifies handling of error and exceptional conditions.

finds

Monitoring may detect symptoms of unhandled conditions but does not eliminate the root weakness.

prevents

Secure coding standards directly mandate proper checks for exceptional and unusual conditions.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-754, a class-level weakness. Rules are authored against its narrower children: CWE-354.

References