Linux · Linux kernel · CWE-754 · published 2025-09-05
CVE-2025-39682Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability
Patch today Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
CVE-2025-39682 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-18. EPSS estimates a 3.3% chance of exploitation in the next 30 days, higher than 88% of all CVEs. This Linux kernel vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Patched packages are out for Debian, Ubuntu and Red Hat Enterprise Linux. US federal agencies must remediate by 2026-09-21. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA 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. (federal due date 2026-09-21)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | linux | Fixed in 6.12.48-1 |
| 12 bookworm | linux | Fixed in 6.1.153-1 | |
| Ubuntu (+119 more packages) | 24.04 LTS | linux | Fixed in 6.8.0-86.87 |
| Red Hat Enterprise Linux | RHEL 10 | kernel | Fixed in 6.12.0-55.37.1.el10_0 RHSA-2025:16904 |
| RHEL 9 | kernel | Fixed in 5.14.0-570.49.1.el9_6 RHSA-2025:16880 | |
| RHEL 8 | kernel | Not affected | |
| RHEL 8 | kernel-rt | Not affected | |
| RHEL 7 | kernel | Not affected | |
| RHEL 7 | kernel-rt | Not affected | |
| RHEL 6 | kernel | Not affected |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Operating systemLinux kernel
Improper Check for Unusual or Exceptional ConditionsCVE-2025-39682
Why: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2026-09-18 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 3.3% (89th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-754: Improper Check for Unusual or Exceptional Conditions
More from this vendor: all Linux vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Linux Linux
84c61fe1a75b4255df1e1e7c054c9e6d048da417to before2902c3ebcca52ca845c03182000e8d71d3a5196f(affected)84c61fe1a75b4255df1e1e7c054c9e6d048da417to beforec09dd3773b5950e9cfb6c9b9a5f6e36d06c62677(affected)84c61fe1a75b4255df1e1e7c054c9e6d048da417to before3439c15ae91a517cf3c650ea15a8987699416ad9(affected)84c61fe1a75b4255df1e1e7c054c9e6d048da417to before29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e(affected)84c61fe1a75b4255df1e1e7c054c9e6d048da417to before62708b9452f8eb77513115b17c4f8d1a22ebf843(affected)
- Linux Linux
6.0(affected)0to before6.0(unaffected)6.1.149through6.1.*(unaffected)6.6.103through6.6.*(unaffected)6.12.44through6.12.*(unaffected)6.16.4through6.16.*(unaffected)6.17through*(unaffected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.