LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26800: tls: fix use-after-free on failed backlog decryption

In the Linux kernel, the following vulnerability has been resolved: tls: fix use-after-free on failed backlog decryption When the decrypt request goes to the backlog and crypto_aead_decrypt returns -EBUSY, tls_do_decryption will wait until all async decryptions have completed. If one of them fails, tls_do_decryption will return -EBADMSG and tls_decrypt_sg jumps to the error path, releasing all the pages. But the pages have been passed to the async callback, and have already been released by tls_decrypt_done. The only true async case is when crypto_aead_decrypt returns -EINPROGRESS. With -EBUSY, we already waited so we can tell tls_sw_recvmsg that the data is available for immediate copy, but we need to notify tls_decrypt_sg (via the new ->async_done flag) that the memory has already been released.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-safety bug in kernel TLS handling. Under a failed asynchronous decrypt backlog condition, pages can be released twice or used after release. Business impact is not fully quantified in the sources, but kernel memory errors can affect system stability and potentially security boundaries.

Executive priority

Treat as a kernel patch-management item with uncertain severity. Prioritize normal-to-expedited remediation where Linux systems are exposed, business-critical, or use kernel TLS, but the supplied sources do not justify emergency response claims.

Technical view

The flaw is in Linux kernel TLS software receive decryption. When crypto_aead_decrypt returns -EBUSY, tls_do_decryption waits for async decryptions; if one fails, tls_decrypt_sg follows an error path that releases pages already released by tls_decrypt_done. The fix adds async_done handling to avoid reusing freed memory.

Likely exposure

Exposure appears limited to Linux systems running affected kernel code paths that use kernel TLS receive processing with asynchronous crypto backlog behavior. The bundle names Linux kernel stable commits and versions, but distro-specific affected packages are not provided.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. No public exploit status, attack prerequisites, or practical impact details are provided in the supplied evidence.

Researcher notes

Evidence supports a use-after-free in the TLS receive decrypt error path involving -EBUSY, async completion, and page lifetime tracking. The bundle lacks CVSS, CWE, exploitability analysis, and distro package ranges, so validation should be source-and-vendor specific.

Mitigation direction

  • Check your Linux distribution advisory for CVE-2024-26800 package status.
  • Update kernels to vendor-supported builds containing the referenced upstream stable fixes.
  • Prioritize internet-facing or high-availability Linux systems using kernel TLS features.
  • If no vendor fix is available, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and container hosts.
  • Map installed kernels to distribution advisories for CVE-2024-26800.
  • Confirm whether kernel TLS is enabled or used by workloads.
  • Verify patched systems booted into the updated kernel, not only installed it.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26800 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcd1bbca03f3c1d845ce274c0d0a66de8e5929f72, 13eca403876bbea3716e82cdfe6f1e6febb38754, ab6397f072e5097f267abf5cb08a8004e6b17694, 8590541473188741055d27b955db0777569438e3, 3ade391adc584f17b5570fd205de3ad029090368, 5.15.160unaffected
LinuxLinux6.6.18, 6.7.6unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.