CVE-2024-26585: tls: fix race between tx work scheduling and socket close
In the Linux kernel, the following vulnerability has been resolved:
tls: fix race between tx work scheduling and socket close
Similarly to previous commit, the submitting thread (recvmsg/sendmsg)
may exit as soon as the async crypto handler calls complete().
Reorder scheduling the work before calling complete().
This seems more logical in the first place, as it's
the inverse order of what the submitting thread will do.
Security readout for executives and security teams
Plain-English summary
CVE-2024-26585 is a Linux kernel TLS race condition involving transmit work scheduling during socket close. The public record confirms a kernel fix but does not provide CVSS, exploitability, or business impact details. Treat it as a kernel maintenance risk requiring timely patch review, especially on systems using kernel TLS features.
Executive priority
Handle through normal-to-expedited kernel patch governance. There is a confirmed fix but insufficient public evidence for emergency action. Prioritize internet-facing, high-availability, and TLS-intensive Linux systems after confirming vendor applicability.
Technical view
The issue is in Linux kernel TLS. A recvmsg/sendmsg submitting thread may exit after an async crypto handler calls complete(), creating a race with socket close. The fix reorders work scheduling before completion. Public sources list affected Linux versions and stable kernel commits but do not define a CWE or CVSS score.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions and code paths using kernel TLS with async crypto. The source data lists Linux as affected, including versions around 4.20 through 6.8, but exact distro-specific impact should be verified against vendor advisories.
Exploitation context
CISA KEV is false in the provided data, and the cited sources do not report active exploitation or public exploit availability. The sources do not establish remote exploitability, required privileges, or likely impact such as crash, privilege escalation, or data exposure.
Researcher notes
The record lacks CVSS, CWE, and impact characterization. Analysis should focus on the kernel TLS async crypto completion ordering and whether downstream kernels have backported the stable commits. Avoid assuming exploitability beyond the race described in the kernel advisory text.
Mitigation direction
Update affected Linux kernels through your distribution or stable kernel channel.
Prioritize systems using kernel TLS or heavy TLS offload paths.
Review the referenced stable kernel commits for backport status.
Track Fedora and other vendor advisories for packaged fixes.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Check whether deployed kernels include the referenced stable fixes.
Confirm distribution security advisories mark the package fixed.
Identify workloads using kernel TLS where possible.
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-26585 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.