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.
CVSS
No CVSS.
References
Configurations
No configuration.
History
28 Aug 2025, 15:15
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
28 Aug 2025, 10:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-08-28 10:15
Updated : 2025-08-29 16:24
NVD link : CVE-2024-58240
Mitre link : CVE-2024-58240
CVE.ORG link : CVE-2024-58240
JSON object : View
Products Affected
No product.
CWE
No CWE.