tls: separate no-async decryption request handling from async

Summary

In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.

Timeline

1. Aug 28, 2025, 9:40 AM UTCCVE published
2. Oct 15, 2026, 9:42 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: total

3. Oct 15, 2026, 9:51 PM UTCRecord last updated

Affected versions

• Linux Linux

  From 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 · fixed in f32ab6cb544d01cdc150de5df389ac685aa507b0; From 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 · fixed in 5f7761c94b1db7570cab328c9f940a33284509b7; From 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 · fixed in 48905146d11dbf1ddbb2967319016a83976953f5; From 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 · fixed in dec5b6e7b211e405d3bcb504562ab21aa7e5a64d; From 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 · fixed in 999115298017a675d8ddf61414fc7a85c89f1186; From 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 · fixed in 41532b785e9d79636b3815a64ddf6a096647d011

• Linux Linux

  4.13

• KernelLinux

  From 4.13.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.149; From 6.2.0 · fixed in 6.6.21; From 6.7.0 · fixed in 6.7.9

References 6