UBUNTU-CVE-2025-38616
In the Linux kernel, the following vulnerability has been resolved: tls: handle data disappearing from under the TLS ULP TLS expects that it owns the receive queue of the TCP socket. This cannot be guaranteed in case the reader of the TCP socket entered before the TLS ULP was installed, or uses some non-standard read API (eg. zerocopy ones). Replace the WARN_ON() and a buggy early exit (which leaves anchor pointing to a freed skb) with real error handling. Wipe the parsing state and tell the reader to retry. We already reload the anchor every time we (re)acquire the socket lock, so the only condition we need to avoid is an out of bounds read (not having enough bytes in the socket for previously parsed record len). If some data was read from under TLS but there's enough in the queue we'll reload and decrypt what is most likely not a valid TLS record. Leading to some undefined behavior from TLS perspective (corrupting a stream? missing an alert? missing an attack?) but no kernel crash should take place.
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
13 explicit affected versions
12 explicit affected versions
7 explicit affected versions
12 explicit affected versions
4 explicit affected versions
10 explicit affected versions
26 explicit affected versions
30 explicit affected versions
23 explicit affected versions
19 explicit affected versions
6 explicit affected versions
24 explicit affected versions
10 explicit affected versions
25 explicit affected versions
26 explicit affected versions
7 explicit affected versions
29 explicit affected versions
13 explicit affected versions
32 explicit affected versions
35 explicit affected versions
18 explicit affected versions
34 explicit affected versions
35 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
40 explicit affected versions
1 explicit affected versions
9 explicit affected versions
21 explicit affected versions
9 explicit affected versions
16 explicit affected versions
10 explicit affected versions
36 explicit affected versions
8 explicit affected versions
7 explicit affected versions
12 explicit affected versions
9 explicit affected versions
7 explicit affected versions
12 explicit affected versions
14 explicit affected versions
10 explicit affected versions
1 explicit affected versions
7 explicit affected versions
6 explicit affected versions
12 explicit affected versions
12 explicit affected versions
29 explicit affected versions
11 explicit affected versions
22 explicit affected versions
22 explicit affected versions
10 explicit affected versions
37 explicit affected versions
8 explicit affected versions
13 explicit affected versions
28 explicit affected versions
3 explicit affected versions
10 explicit affected versions
9 explicit affected versions
26 explicit affected versions
2 explicit affected versions
13 explicit affected versions
29 explicit affected versions
13 explicit affected versions
10 explicit affected versions
29 explicit affected versions
29 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
8 explicit affected versions
7 explicit affected versions
11 explicit affected versions
5 explicit affected versions
34 explicit affected versions
16 explicit affected versions
38 explicit affected versions
3 explicit affected versions
7 explicit affected versions
51 explicit affected versions
18 explicit affected versions
30 explicit affected versions
12 explicit affected versions
27 explicit affected versions
31 explicit affected versions
8 explicit affected versions
5 explicit affected versions
3 explicit affected versions
8 explicit affected versions
10 explicit affected versions
7 explicit affected versions
34 explicit affected versions
13 explicit affected versions
13 explicit affected versions
7 explicit affected versions
8 explicit affected versions
10 explicit affected versions
12 explicit affected versions
7 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
37 explicit affected versions
39 explicit affected versions
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
11 explicit affected versions
27 explicit affected versions
10 explicit affected versions
8 explicit affected versions
7 explicit affected versions
4 explicit affected versions
1 explicit affected versions
13 explicit affected versions
43 explicit affected versions
10 explicit affected versions
8 explicit affected versions
33 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
11 explicit affected versions
1 explicit affected versions
7 explicit affected versions
27 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: tls: handle data disappearing from under the TLS ULP TLS expects that it owns the receive queue of the TCP socket. This cannot be guaranteed in case the reader of the TCP socket entered before the TLS ULP was installed, or uses some non-standard read API (eg. zerocopy ones). Replace the WARN_ON() and a buggy early exit (which leaves anchor pointing to a freed skb) with real error handling. Wipe the parsing state and tell the reader to retry. We already reload the anchor every time we (re)acquire the socket lock, so the only condition we need to avoid is an out of bounds read (not having enough bytes in the socket for previously parsed record len). If some data was read from under TLS but there's enough in the queue we'll reload and decrypt what is most likely not a valid TLS record. Leading to some undefined behavior from TLS perspective (corrupting a stream? missing an alert? missing an attack?) but no kernel crash should take place.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/6db015fc4b5d5f63a64a193f65d98da3a7fc811d
- https://git.kernel.org/stable/c/2fb97ed9e2672b4f6e24ce206ac1a875ce4bcb38
- https://git.kernel.org/stable/c/6db015fc4b5d5f63a64a193f65d98da3a7fc811d
- https://git.kernel.org/stable/c/db3658a12d5ec4db7185ae7476151a50521b7207
- https://git.kernel.org/stable/c/eb0336f213fe88bbdb7d2b19c9c9ec19245a3155
- https://ubuntu.com/security/CVE-2025-38616
- https://ubuntu.com/security/notices/USN-7879-1
- https://ubuntu.com/security/notices/USN-7879-2
- https://ubuntu.com/security/notices/USN-7879-3
- https://ubuntu.com/security/notices/USN-7879-4
- https://ubuntu.com/security/notices/USN-7880-1
- https://ubuntu.com/security/notices/USN-7889-1
- https://ubuntu.com/security/notices/USN-7889-2
- https://ubuntu.com/security/notices/USN-7889-3
- https://ubuntu.com/security/notices/USN-7889-4
- https://ubuntu.com/security/notices/USN-7889-5
- https://ubuntu.com/security/notices/USN-7889-6
- https://ubuntu.com/security/notices/USN-7889-7
- https://ubuntu.com/security/notices/USN-7934-1
- https://ubuntu.com/security/notices/USN-7935-1
- https://ubuntu.com/security/notices/USN-7940-1
- https://ubuntu.com/security/notices/USN-7940-2
- https://www.cve.org/CVERecord?id=CVE-2025-38616