MSRXCVE-2025-39682
CVE-2025-39682
tls: fix handling of zero-length records on the rx_list
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.
CVSS 3.1 · CNA
chance of exploitation in the next 30 days (EPSS; higher than 88% of CVEs)
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.
Scores
Affected packages and fixed versions
| Package | Ecosystem | Fixed in |
|---|---|---|
| Kernel | Linux | 6.1.149, 6.6.103, 6.12.44, 6.16.4 |
Affected products
- Linux Linux: 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to < 2902c3ebcca52ca845c03182000e8d71d3a5196f; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to < c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to < 3439c15ae91a517cf3c650ea15a8987699416ad9; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to < 29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e; 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to < 62708b9452f8eb77513115b17c4f8d1a22ebf843
- Linux Linux: 6.0
Also known as: A-440544511, ASB-A-440544511
5 references (advisories, patches, write-ups)
- 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
Sources: CVE.org, OSV.dev, FIRST EPSS. Missing ones did not answer or have no record yet.