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.
from 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before f32ab6cb544d01cdc150de5df389ac685aa507b0; from 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before 5f7761c94b1db7570cab328c9f940a33284509b7; from 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before 48905146d11dbf1ddbb2967319016a83976953f5; from 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before dec5b6e7b211e405d3bcb504562ab21aa7e5a64d; from 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before 999115298017a675d8ddf61414fc7a85c89f1186; from 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 before 41532b785e9d79636b3815a64ddf6a096647d011
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.