Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability
Linux / Kernel
Linux Kernel contains an improper check for unusual or exceptional conditions vulnerability in the TLS receive path which allows a zero-length record retrieved from the rx_list to bypass the intended recvmsg() record-type handling, potentially causing subsequent TLS records to be processed using incorrect zero-copy and queuing assumptions. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
- CVE identifier
- CVE-2025-39682
- Added to KEV
- Sep 18, 2026
- CISA catalog dueDate
- Sep 21, 2026
The dates above are catalog fields. The addition date does not establish when the vulnerability was discovered or first exploited. Confirm which requirements apply to your organisation separately.
Publisher's 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.
This wording is attributed to the CISA snapshot. Verify current vendor guidance, affected versions and your deployment before applying changes.
Keep the signals separate.
- Ransomware use, as reported by CISA
- Unknown
- CVSS severity
- Not supplied by KEV
- EPSS probability
- 2.88%
EPSS score date: 2026-09-27T12:00:21Z. Percentile: 86.32%. Model version: v2026.06.15.
A dated estimate of exploitation probability over the following 30 days, not a severity score or a probability of a breach in your environment.
Inspect the EPSS source ↗“Unknown” ransomware use is an unknown source field, not proof that ransomware activity has not occurred.
Source notes
This vulnerability affects an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: ; https://git.kernel.org/stable/c/2902c3ebcca52ca845c03182000e8d71d3a5196f; https://git.kernel.org/stable/c/c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677; https://git.kernel.org/stable/c/3439c15ae91a517cf3c650ea15a8987699416ad9; https://git.kernel.org/stable/c/29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e; https://git.kernel.org/stable/c/62708b9452f8eb77513115b17c4f8d1a22ebf843 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2025-39682
Source & freshness
Source updated: Sep 27, 2026, 9:30 PM UTC
Successfully checked: Sep 27, 2026, 11:50 PM UTC
This snapshot is older than 36 hours. Check current publisher guidance.
Automated source record, not an editorial advisory or an independent discovery. No affected or fixed version is inferred, and no organisation-specific risk rating is generated.