CVE-2024-58239: tls: stop recv() if initial process_rx_list gave us non-DATA
In the Linux kernel, the following vulnerability has been resolved:
tls: stop recv() if initial process_rx_list gave us non-DATA
If we have a non-DATA record on the rx_list and another record of the
same type still on the queue, we will end up merging them:
- process_rx_list copies the non-DATA record
- we start the loop and process the first available record since it's
of the same type
- we break out of the loop since the record was not DATA
Just check the record type and jump to the end in case process_rx_list
did some work.
Security readout for executives and security teams
Plain-English summary
CVE-2024-58239 is a Linux kernel flaw in kernel TLS receive handling. Under specific queued TLS record conditions, non-DATA records can be merged incorrectly. The public record says it is resolved, but does not provide CVSS, CWE, or business-impact detail.
Executive priority
Treat as a patch-management item until impact data improves. Prioritize internet-facing or high-throughput TLS infrastructure, but avoid emergency escalation unless vendor guidance adds severity or exploitation evidence.
Technical view
The flaw is in the Linux kernel TLS rx_list path. If process_rx_list copied a non-DATA record and another record of the same type remained queued, recv() could merge them before stopping. The fix stops recv() when initial rx_list processing produced non-DATA.
Likely exposure
Exposure appears limited to Linux systems using affected kernel versions and the kernel TLS receive path. The source bundle lists Linux as affected but provides no CPEs or distribution-specific package mapping.
Exploitation context
No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the bundle includes no public exploit status, exploitability analysis, or impact rating.
Researcher notes
The record identifies a logic error in TLS record handling but omits CVSS, CWE, and concrete impact. Validate by branch-specific kernel commit presence, not by the repeated raw upstream hash values alone.
Mitigation direction
Update affected Linux kernels to vendor builds containing the cited stable fixes.
Check Linux distribution advisories for exact fixed package versions.
Prioritize systems running TLS workloads that may use kernel TLS.
If immediate patching is unavailable, 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-58239.
Confirm the relevant stable fix commit is present in deployed kernel sources or changelogs.
Identify workloads or modules that rely on kernel TLS receive handling.
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-58239 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
0ADP providers
8Source links
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.
Aug 22, 2025, 13:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.