In tls_sw_recvmsg of tls_sw.c, there is a possible use after free due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-39682US | critical9.8OT critical | KEV | ||
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 contig… | ||||
02
references
External citations — patches, advisories, analysis.
- https://android.googlesource.com/kernel/common/+/2902c3ebcca52ca845c03182000e8d71d3a5196fFIX
- https://android.googlesource.com/kernel/common/+/3439c15ae91a517cf3c650ea15a8987699416ad9FIX
- https://android.googlesource.com/kernel/common/+/74715c47d57ccbff2f2f00bb9d87288e10642325FIX
- https://source.android.com/security/bulletin/2026-03-01ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan