dbcve.org
Linux KernelOperating system · Linux

CVE-2024-27431

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 5.10.213 / 5.15.152 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-908

Memory or a resource is used before it has been initialised, so its contents are whatever happened to be there — sometimes leaking earlier data, sometimes values an attacker can influence. Behaviour becomes unpredictable and occasionally exploitable. Remediation is initialising every resource before use and ensuring initialisation happens on all code paths.

General guidance for the use of uninitialized resource class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.9, < 5.10.213>= 5.11, < 5.15.152>= 5.16, < 6.1.82>= 6.2, < 6.6.22>= 6.7, < 6.7.10= 6.8
Debian LinuxOperating system
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.213 / 5.15.152 / 6.1.82 or later
Fixed in 5.10.2135.15.1526.1.82
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 5.10.213, 5.15.152, 6.1.82, or 6.6.22 (or later stable release) depending on your current branch

  1. Identify your current kernel version using `uname -r`
  2. Check which vulnerable version range your kernel falls into (5.9 to 5.10.212, 5.11 to 5.15.151, 5.16 to 6.1.81, or 6.2 to 6.6.21)
  3. For kernels in the 5.10.x branch: upgrade to kernel version 5.10.213 or later
  4. For kernels in the 5.11-5.15.x branch: upgrade to kernel version 5.15.152 or later
  5. For kernels in the 5.16-6.1.x branch: upgrade to kernel version 6.1.82 or later
  6. For kernels in the 6.2-6.6.x branch: upgrade to kernel version 6.6.22 or later
  7. Reboot the system to load the new kernel
  8. Verify the fix is applied by checking that the cpumap code now zero-initializes xdp_rxq_info before use
Caveat Kernel upgrades may require rebuilding third-party kernel modules; ensure driver compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27431 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data