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.
https://git.kernel.org/stable/c/dec5b6e7b211e405d3bcb504562ab21aa7e5a64d
https://git.kernel.org/stable/c/999115298017a675d8ddf61414fc7a85c89f1186
https://git.kernel.org/stable/c/48905146d11dbf1ddbb2967319016a83976953f5
https://git.kernel.org/stable/c/41532b785e9d79636b3815a64ddf6a096647d011