# CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues

> A missing check in the GVE network driver allows a null pointer dereference or divide-by-zero error, causing a kernel crash when XDP queues are absent.

- **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 Jan 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2024-57932, DEBIAN-CVE-2024-57932, GHSA-4hjr-56f9-j54w, UBUNTU-CVE-2024-57932

## What is CVE-2024-57932?

CVE-2024-57932 is a critical vulnerability in Linux kernel, published on 21 Jan 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:

gve: guard XDP xmit NDO on existence of xdp queues

In GVE, dedicated XDP queues only exist when an XDP program is installed
and the interface is up. As such, the NDO XDP XMIT callback should
return early if either of these conditions are false.

In the case of no loaded XDP program, priv->num_xdp_queues=0 which can
cause a divide-by-zero error, and in the case of interface down,
num_xdp_queues remains untouched to persist XDP queue count for the next
interface up, but the TX pointer itself would be NULL.

The XDP xmit callback also needs to synchronize with a device
transitioning from open to close. This synchronization will happen via
the GVE_PRIV_FLAGS_NAPI_ENABLED bit along with a synchronize_net() call,
which waits for any RCU critical sections at call-time to complete.

Weakness: CWE-369 (Divide By Zero)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-57932 being exploited?

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

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

## Sources

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

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