tls: separate no-async decryption request handling from async
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 · < 41532b785e9d79636b3815a64ddf6a096647d011| No fix yet |
| Linux Linux |
|
|
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 the CVE record · Linux
The Linux kernel’s TLS code has a vulnerability involving decryption request handling. The description does not establish what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Administrators running Linux kernel versions affected by CVE-2024-58240 should check their exposure; specific versions are not provided.