# CVE-2024-39293: Revert "xsk: Support redirect to any socket bound to the same umem"

> A race condition in the Linux kernel's AF_XDP implementation allows concurrent access to Rx rings, leading to state corruption and kernel crashes.

- **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:** 25 Jun 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-39293, DEBIAN-CVE-2024-39293, GHSA-vhxr-pcmq-x8rc, ROOT-OS-UBUNTU-2204-CVE-2024-39293, ROOT-OS-UBUNTU-2404-CVE-2024-39293, UBUNTU-CVE-2024-39293

## What is CVE-2024-39293?

CVE-2024-39293 is a critical vulnerability in Linux kernel, published on 25 Jun 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:

Revert "xsk: Support redirect to any socket bound to the same umem"

This reverts commit 2863d665ea41282379f108e4da6c8a2366ba66db.

This patch introduced a potential kernel crash when multiple napi instances
redirect to the same AF_XDP socket. By removing the queue_index check, it is
possible for multiple napi instances to access the Rx ring at the same time,
which will result in a corrupted ring state which can lead to a crash when
flushing the rings in __xsk_flush(). This can happen when the linked list of
sockets to flush gets corrupted by concurrent accesses. A quick and small fix
is not possible, so let us revert this for now.

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

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-39293 being exploited?

There is no known exploitation of CVE-2024-39293 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-39293 and fix it if it is affected.

What it is: CVE-2024-39293 is a critical vulnerability in Linux kernel, published on 25 Jun 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-39293 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-39293/ (Markdown: https://insights.sbomify.com/CVE-2024-39293/index.md)
```

## Sources

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

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