CVE-2024-58240
Linux Kernel use-after-free
- Published28 Aug 2025
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://git.kernel.org/stable/c/41532b785e9d79636b3815a64ddf6a096647d011
- https://git.kernel.org/stable/c/48905146d11dbf1ddbb2967319016a83976953f5
- https://git.kernel.org/stable/c/5f7761c94b1db7570cab328c9f940a33284509b7
- https://git.kernel.org/stable/c/999115298017a675d8ddf61414fc7a85c89f1186
- https://git.kernel.org/stable/c/dec5b6e7b211e405d3bcb504562ab21aa7e5a64d
- https://git.kernel.org/stable/c/f32ab6cb544d01cdc150de5df389ac685aa507b0
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-58240 being actively exploited?
CVE-2024-58240 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.33%.
How severe is CVE-2024-58240?
CVE-2024-58240 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.33% probability of exploitation.
Which products are affected by CVE-2024-58240?
Affected products include Debian Linux, Linux Kernel.
How do I fix CVE-2024-58240?
Upgrade affected software to a fixed version, for example Linux Kernel 6.1.149 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-58240 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.