dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53031

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.12.91 / 6.18.33 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available 8 weeks old

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: bpf: Validate node_id in arena_alloc_pages() arena_alloc_pages() accepts a plain int node_id and forwards it through the entire allocation chain without any bounds checking. Validate node_id before passing it down the allocation chain in arena_alloc_pages().

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 · moderate confidence

The arena_alloc_pages() function in the Linux kernel's BPF subsystem accepts a node_id parameter that is passed through the entire allocation chain without validation. An attacker could potentially pass an out-of-bounds node_id value, leading to memory corruption, out-of-bounds access, or denial of service. The fix requires adding bounds checking on node_id before it's used in the allocation path.

MitigationApply the kernel patch that adds node_id validation in arena_alloc_pages(). This is a single-point validation fix that should prevent invalid NUMA node IDs from propagating through the allocation chain.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:>= 6.9, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

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
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed kernel version
    Run 'uname -r' or check /proc/version to obtain the running kernel version
    Affected if The version falls within >= 6.9, < 6.12.91 OR >= 6.13, < 6.18.33 OR >= 6.19, < 7.0.10
  2. Verify BPF subsystem is enabled
    Check if BPF is loaded: 'lsmod | grep bpf' or check /sys/kernel/debug/tracing/events/bpf/ for existence
    Affected if The BPF subsystem is loaded and active in the kernel
  3. Check for arena_alloc_pages usage
    Inspect kernel symbols: 'cat /proc/kallsyms | grep arena_alloc_pages' or check BPF arena functionality is in use
    Affected if The arena_alloc_pages symbol exists and BPF memory allocator (arena) feature is being used

The system is affected if the running kernel version is within the affected ranges AND the BPF arena subsystem is enabled and utilizing the vulnerable arena_alloc_pages function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 6.12.91 / 6.18.33 / 7.0.10 or later
Fixed in 6.12.916.18.337.0.10
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch that adds node_id validation in arena_alloc_pages(). This is a single-point validation fix that should prevent invalid NUMA node IDs from propagating through the allocation chain.

Recommended fix High confidence

Linux Kernel 6.12.91+ / 6.18.33+ / 7.0.10+ (or later stable release)

  1. Identify the currently running Linux kernel version using 'uname -r'
  2. Based on the affected version ranges, upgrade the kernel to version 6.12.91 or later, OR version 6.18.33 or later, OR version 7.0.10 or later
  3. Apply the appropriate kernel upgrade through your distribution's package manager (e.g., apt-get update && apt-get install linux-image-<version>, yum update kernel, or dnf upgrade kernel)
  4. Reboot the system to load the patched kernel
  5. Verify the kernel version after reboot using 'uname -r' to confirm the patch is applied
Caveat Kernel upgrades may require system reboot and could introduce compatibility changes with external modules or drivers; ensure backup and test in staging if possible

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53031 — 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-2026-53031 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