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

> A race condition in the Linux kernel TLS implementation allows use-after-free, potentially leading to denial of service or code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Feb 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-35474, AZL-35799, AZL-35812, BELL-CVE-2024-26583, DEBIAN-CVE-2024-26583, GHSA-j737-8h5g-42g9, ROOT-OS-DEBIAN-11-CVE-2024-26583, UBUNTU-CVE-2024-26583

## What is CVE-2024-26583?

CVE-2024-26583 is a critical vulnerability in Linux kernel, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2024-26583?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-26583?

Apply the vendor's patch.

## Is CVE-2024-26583 being exploited?

There is no known exploitation of CVE-2024-26583 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26583 and fix it if it is affected.

What it is: CVE-2024-26583 is a critical vulnerability in Linux kernel, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26583 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26583/ (Markdown: https://insights.sbomify.com/CVE-2024-26583/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26583
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26583
- OSV: https://osv.dev/vulnerability/CVE-2024-26583

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26583/
Summaries are generated and may contain mistakes; the official description above is the record.