CVE-2024-58240

Medium

Elevated severity or exploit probability.

CVSS base

9.8 CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS — probability of exploitation (30 days)

0.3%

26.1th percentile

CISA KEV

Not listed

Weakness / dates

CWE-416

Published 2025-08-28 · modified 2026-08-19

CVSS breakdown

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector	N	Network
Attack Complexity	L	Low
Privileges Required	N	None
User Interaction	N	None
Scope	U	Unchanged
Confidentiality	H	High
Integrity	H	High
Availability	H	High

Timeline

2025-08-28 — Published (NVD)
2026-08-19 — Last modified (NVD)

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

debian linux

References

Official: NVD · CVE.org