LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26583: tls: fix race between async notify and socket close

In the Linux kernel, the following vulnerability has been resolved: tls: fix race between async notify and socket close The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto handler calls complete() so any code past that point risks touching already freed data. Try to avoid the locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we are now tightly controlling when completion fires.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26583 is a Linux kernel race condition in TLS handling. A thread using send or receive can exit after async crypto completion, while later code may touch freed data. Business risk is mainly kernel stability and memory-safety exposure on affected Linux systems, but public sources do not provide CVSS severity or exploitation evidence.

Executive priority

Track and patch through normal kernel update processes, with faster handling for exposed or TLS-intensive Linux infrastructure. Escalation beyond standard patch urgency is not supported by the provided evidence.

Technical view

The issue is in Linux kernel TLS async notification versus socket close handling. The fix changes synchronization by holding an extra reference and relying on the atomic reference counter, avoiding completion reuse and post-completion access to freed state. The CVE record lists affected Linux kernel versions and multiple stable-tree fixes.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with kernel TLS paths in use. The source bundle does not identify specific distributions beyond a Fedora package advisory, nor does it prove exposure for all Linux deployments.

Exploitation context

The source bundle states KEV is false and provides no public exploit evidence. Treat this as a kernel memory-safety race requiring patch validation, not as confirmed active exploitation.

Researcher notes

Evidence supports a resolved race in kernel TLS async crypto completion and socket close. Impact details, exploit prerequisites, and practical exploitability are not described in the supplied sources, so validation should focus on kernel version and vendor backport status.

Mitigation direction

  • Apply vendor kernel updates containing the listed stable fixes.
  • Use distribution advisories to confirm the corrected package version.
  • Prioritize systems using Linux kTLS or TLS-heavy workloads.
  • If patching is delayed, check vendor guidance for supported mitigations.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Compare installed kernels against vendor fixed package advisories.
  • Review kernel changelogs for the CVE or fix title.
  • Confirm patched systems boot the updated kernel successfully.
Prepared
Confidence
medium
Sources
8

Public sources used

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-26583 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
7Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0cada33241d9de205522e3858b18e506ca5cce2c, 0cada33241d9de205522e3858b18e506ca5cce2c, 0cada33241d9de205522e3858b18e506ca5cce2c, 0cada33241d9de205522e3858b18e506ca5cce2c, 0cada33241d9de205522e3858b18e506ca5cce2c, cf4cc95a15f599560c7abd89095a7973a4b9cec3, 9b81d43da15e56ed89f083f326561acdcaf549ce, 5.4.44, 5.6.16unaffected
LinuxLinux5.7, 0, 5.15.160, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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