Critical· 9.8official fix available
CVE-2024-26800
A flaw in the Linux kernel's TLS (Transport Layer Security) implementation allows for a 'use-after-free' error. This occurs when the system incorrectly handles memory during a failed decryption process.
publishedApr 4, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
51th 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
Users running Linux kernel version 6.8 or affected versions of the Linux kernel.
02
Real-world impact
An attacker could potentially exploit this memory error to cause a system crash or execute arbitrary code, potentially gaining control over the affected system.
03
Why this severity
The critical score reflects that this vulnerability is easy to exploit remotely without authentication and can lead to a total loss of confidentiality, integrity, and availability.
04
What to do about it
official fix available
recommended steps
- 01Update the Linux kernel to a version that includes the fix for the tls: fix use-after-free on failed backlog decryption vulnerability.
NVD-referenced vendor advisory
05
Timeline
- Apr 4, 2024 · Apr 4, 2024PublishedDisclosed and added to the National Vulnerability Database.
- Aug 4, 2026 · 2d agoAdvisory updatedThe NVD record was last revised.
- Aug 5, 2026 · 22h agoOfficial fix availableA 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 →