Known exploited vulnerability
CVE-2025-39682
The short answer
CVE-2025-39682 affects Linux Linux and is rated critical (CVSS 9.8). CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-18: attackers are using it, so patch it first. The vendor has linked a patch.
What it is
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.
Weakness: CWE-754.
Severity
9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploited (CISA KEV)
Yes, since Sep 18, 2026
Federal due date Sep 21, 2026
EPSS, next 30 days
3.3%
Higher than 89% of scored CVEs
How it can be exploited
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
What CISA says to do
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…
Affected products
Linux, SIMATIC CN 4100. NVD's record lists the exact affected versions.
References
- git.kernel.org/stable/c/2902c3ebcca52ca845c03182000e8d71d3a5196f Patch
- git.kernel.org/stable/c/29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e Patch
- git.kernel.org/stable/c/3439c15ae91a517cf3c650ea15a8987699416ad9 Patch
- git.kernel.org/stable/c/62708b9452f8eb77513115b17c4f8d1a22ebf843 Patch
- git.kernel.org/stable/c/c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677 Patch
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html Mailing ListThird Party Advisory
- cert-portal.siemens.com/productcert/html/ssa-032379.html Third Party Advisory
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-39682 US Government Resource
Questions
Is CVE-2025-39682 being exploited?
Yes. CISA added CVE-2025-39682 to its Known Exploited Vulnerabilities catalog on 2026-09-18, with a federal remediation due date of 2026-09-21.
How do I fix CVE-2025-39682?
CISA'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…
From NVD, CISA KEV, FIRST EPSS and OSV.dev, checked . Status on NVD: Analyzed. The description is NVD's text, quoted as published.
Related
Latest CVEs this week
Critical and High CVEs from the last 7 days, with KEV and EPSS.
Exploited vulnerabilities by vendor
Every vendor in CISA's KEV catalog, with its count.
Linux exploited vulnerabilities
Everything CISA lists as exploited for Linux.
Vulnerability watch
A briefing and a fix pull request when an advisory hits your dependencies.
Know the day a CVE lands in your code
Connect a GitHub repository and ZeusQA checks its dependencies daily, briefs each advisory and opens the fix. Three test runs free, no card.