What’s Vulnerable › Vulnerabilities

CVE-2024-58240: tls: separate no-async decryption request handling from async

• Severity: high (CVSS 7.8 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2025-08-28 · updated 2026-10-15
• Weakness: CWE-416

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.

Affected products

• Debian Linux: 11.0
• Linux kernel: from 4.13 before 6.1.149; from 6.2 before 6.6.21; from 6.7 before 6.7.9; 6.8-rc1, 6.8-rc2, 6.8-rc3, 6.8-rc4, 6.8-rc5, 6.8-rc6 — fixed in 6.1.149, 6.6.21, 6.7.9

How to fix

Upgrade to a fixed version: Linux kernel 6.1.149, 6.6.21, 6.7.9. Check the vendor advisory for mitigations.

References

• 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
• https://cert-portal.siemens.com/productcert/html/ssa-032379.html

Get alerted when CVE-2024-58240 or the next vulnerability affects your stack