Description
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.
Product status
3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before 48905146d11dbf1ddbb2967319016a83976953f5
3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before dec5b6e7b211e405d3bcb504562ab21aa7e5a64d
3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before 999115298017a675d8ddf61414fc7a85c89f1186
3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before 41532b785e9d79636b3815a64ddf6a096647d011
4.13
Any version before 4.13
6.1.149
6.6.21
6.7.9
6.8
References
git.kernel.org/...c/48905146d11dbf1ddbb2967319016a83976953f5
git.kernel.org/...c/dec5b6e7b211e405d3bcb504562ab21aa7e5a64d
git.kernel.org/...c/999115298017a675d8ddf61414fc7a85c89f1186
git.kernel.org/...c/41532b785e9d79636b3815a64ddf6a096647d011
