CVE-2024-58240

tls: separate no-async decryption request handling from async

HIGH
7.8
CVSS Score
Published: August 28, 2025 at 09:40 AM UTC
Updated: October 15, 2026 at 10:18 PM UTC
3 products affected across 3 vendorsLinux KernelDebian LinuxSIMATIC CN 4100

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.13 ≤ v < 6.1.1496.2 ≤ v < 6.6.216.7 ≤ v < 6.7.93c4d7559159bfe1e3b94df3a657b2cda3a34e2186.86.8 rc16.8 rc26.8 rc36.8 rc46.8 rc56.8 rc6
Vendor states this is fixed in 41532b785e9d79636b3815a64ddf6a096647d011 (fixed)
Vendor states this is fixed in 48905146d11dbf1ddbb2967319016a83976953f5 (fixed)
Vendor states this is fixed in 5f7761c94b1db7570cab328c9f940a33284509b7 (fixed)
Vendor states this is fixed in 999115298017a675d8ddf61414fc7a85c89f1186 (fixed)
Vendor states this is fixed in dec5b6e7b211e405d3bcb504562ab21aa7e5a64d (fixed)
Vendor states this is fixed in f32ab6cb544d01cdc150de5df389ac685aa507b0 (fixed)
Vendor states this is fixed in 4.13 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.149 (unaffected)
Vendor states this is fixed in 6.6.21 (unaffected)
Vendor states this is fixed in 6.7.9 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)
v < V5.0
Affected range stops below V5.0, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitAutomatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card