Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2024-26583

This vulnerability is a race condition in the Linux kernel’s TLS implementation that can allow an attacker to crash the system or potentially execute arbitrary code. It occurs when asynchronous crypto notifications and socket closures happen concurrently, leading to a use‑after‑free error. The issue has been fixed in recent kernel updates.

publishedFeb 21, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
43th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 4, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel (all distributions) – any system running a kernel version before the patch that contains the race condition in the TLS async notification handling.

02

Real-world impact

An attacker could crash the system or potentially execute arbitrary code by exploiting the race condition, leading to denial of service or privilege escalation.

03

Why this severity

The CVSS score of 9.8 reflects the high impact of the vulnerability: it can be exploited remotely with no authentication or user interaction, and it can compromise confidentiality, integrity, and availability of the affected system.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade your Linux kernel to a version that includes the CVE-2024-26583 fix.
  2. 02Reboot or reload the kernel to apply the update.

NVD-referenced vendor advisory

05

Timeline

  1. Feb 21, 2024 · Feb 21, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 5, 2026 · 8h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →