# CVE-2024-58239: tls: stop recv() if initial process_rx_list gave us non-DATA

> A logic error in the Linux kernel TLS implementation can cause improper record merging, potentially leading to a denial of service.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 22 Aug 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2024-58239, DEBIAN-CVE-2024-58239, GHSA-255m-8v4r-mcgr, UBUNTU-CVE-2024-58239

## What is CVE-2024-58239?

CVE-2024-58239 is a high-severity denial of service vulnerability in Linux kernel, published on 22 Aug 2025. 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: 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.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-58239 being exploited?

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

Public exploit code:

- A variant of CVE-2024-58239 (github_poc): https://github.com/khoatran107/cve-2025-39682
- https://github.com/khoatran107/cve-2024-58239 (github_poc): https://github.com/khoatran107/cve-2024-58239

## 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-58239 and fix it if it is affected.

What it is: CVE-2024-58239 is a high-severity denial of service vulnerability in Linux kernel, published on 22 Aug 2025. 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-58239 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-58239/ (Markdown: https://insights.sbomify.com/CVE-2024-58239/index.md)
```

## Sources

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

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