Look up another CVE · open CVE-2026-53031 in the interactive tracker
CVE-2026-53031
bpf: Validate node_id in arena_alloc_pages()
Published 2026-06-24 (4 months ago) by the Linux kernel CNA. Subsystem kernel/bpf. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-53031 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
kernel/bpf/arena.c
- What this is
- BPF [GENERAL] (Safe Dynamic Programs and Tools)MAINTAINERS section matched on kernel/bpf/ · bpf@vger.kernel.org · Supported
Check it on the machine
grep -wE 'CONFIG_BPF|CONFIG_BPF_SYSCALL' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this code. Every release with an answer below compiles the affected file into the kernels it ships. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sidy
- ?
- not established - no Makefile entry for the affected file
- y
- built into the kernel image on every flavour - only a patch removes it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_BPF, CONFIG_BPF_SYSCALL
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-06-24 (4 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- kernel/bpf
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.9 | 6.12.91 | 31d3b4b28e55 |
| 6.9 | 6.18.33 | e15900888c09 |
| 6.9 | 7.0.10 | fb66e20130f9 |
| 6.9 | 7.1 | 2845989f2eba |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- An attacker must use local BPF syscalls to create/use a BPF arena map and load/execute a BPF program that calls the arena kfunc. The vulnerable path is not reachable directly from network, adjacent, or physical input.
- AC:LAttack complexity, low
- The attacker directly controls the `node_id` argument passed to `bpf_arena_alloc_pages()` and can repeatedly trigger the BPF program. No race or external condition is required.
- PR:LPrivileges required, low
- Using BPF arena requires BPF privileges (`CAP_BPF` and `CAP_PERFMON`) or a delegated BPF token, which can be available to a namespaced/container user in a reasonable deployment. Under the required higher-severity tie-break rule, this is scored as low rather than high privilege.
- UI:NUser interaction, none
- No victim action is required after the attacker has local ability to load and run the BPF program. The attacker can trigger the kfunc directly through BPF execution.
- S:UScope, unchanged
- The vulnerable component and impacted resource are both the local kernel. This is standard local kernel compromise/DoS scope, not a VM or hardware boundary crossing.
- C:HConfidentiality impact, high
- The unchecked `node_id` flows into NUMA allocator metadata lookup (`NODE_DATA`/zonelists), creating out-of-bounds or invalid kernel memory access rather than a bounded harmless failure. Under the higher-severity rule, allocator metadata misuse is treated as potentially enabling high-impact information disclosure.
- I:HIntegrity impact, high
- Invalid NUMA allocator state can cause the page allocator to operate on bogus per-node/zone structures, which can plausibly corrupt kernel allocator state. Under the higher-severity rule, this is scored as potential high-integrity kernel memory corruption.
- A:HAvailability impact, high
- Invalid negative, out-of-range, or offline node IDs can hit allocator assertions, NULL/invalid dereferences, or corrupted zonelist traversal, causing an oops/panic. The attacker can trigger this repeatedly from the malicious BPF program.