CVE-2024-26582: net: tls: fix use-after-free with partial reads and async decrypt
In the Linux kernel, the following vulnerability has been resolved:
net: tls: fix use-after-free with partial reads and async decrypt
tls_decrypt_sg doesn't take a reference on the pages from clear_skb,
so the put_page() in tls_decrypt_done releases them, and we trigger
a use-after-free in process_rx_list when we try to read from the
partially-read skb.
Security readout for executives and security teams
Plain-English summary
CVE-2024-26582 is a Linux kernel flaw in kernel TLS handling. Under specific partial-read and asynchronous decryption conditions, the kernel may access memory after it has been freed. That can cause instability and may have security impact, but the public record does not provide a CVSS score or confirmed exploitation.
Executive priority
Treat as a scheduled kernel remediation item, elevated for Linux systems supporting sensitive or high-availability TLS workloads. There is no sourced evidence of active exploitation, so emergency response is not indicated from the provided record alone.
Technical view
The bug is a use-after-free in Linux kernel net/tls. tls_decrypt_sg does not retain page references from clear_skb; tls_decrypt_done releases them, and process_rx_list later reads from a partially read skb. The issue is fixed in referenced Linux stable commits.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with kernel TLS paths in use, especially receive-side TLS with asynchronous decrypt and partial reads. Systems not using kTLS are less likely to be practically exposed, but kernel version should still drive remediation.
Exploitation context
No CISA KEV listing is provided, and the supplied sources do not report active exploitation. Public details describe the faulty memory lifecycle but do not establish exploitability for privilege escalation, remote code execution, or denial of service.
Researcher notes
The key condition is page lifetime handling during partial reads with async decrypt in net/tls. The public record names the bug and fix commits but lacks CVSS, CWE, exploit status, and detailed affected-range clarity. Validate against upstream stable and distribution-specific kernel metadata.
Mitigation direction
Update Linux kernels using vendor-supported packages or the referenced stable fixes.
Prioritize internet-facing and high-availability Linux workloads that may use kernel TLS.
Review Fedora or other distribution advisories for packaged kernel updates.
If patch timing is unclear, follow your Linux vendor’s guidance.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, appliances, and cloud images.
Compare installed kernels against vendor advisories and the referenced stable commits.
Identify workloads or services that enable kernel TLS features.
Confirm systems rebooted into the remediated kernel after update.
Monitor kernel logs for TLS or memory-corruption related crashes.
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-26582 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 21, 2024, 14:59 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.