Look up another CVE · open CVE-2026-93112 in the interactive tracker
CVE-2026-93112
bpf: Require a BPF cpumask for bpf_cpumask_populate()
Published 2026-09-17 (31 days 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-93112 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 | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
bpf_cpumask_populate() writes to its destination with bitmap_copy(), but the destination is typed as struct cpumask *. That allows the verifier to accept borrowed cpumask pointers returned by read-only kfuncs, such as scx_bpf_get_online_cpumask(), as a writable destination. Make the destination a struct bpf_cpumask * so populate follows the same ownership rule as the other mutating cpumask kfuncs. Query kfuncs continue to accept const struct cpumask * inputs.
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/cpumask.c
tools/sched_ext/include/scx/compat.bpf.h
- 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_JIT|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, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sidYnot built on s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- Y
- built in where it is built at all; some flavours do not build 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_JIT, 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-09-17 (31 days ago)source
- CVSS
- 7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.8% 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.15 | 6.18.52 | 0cfc9348a045 |
| 6.15 | 7.2.6 | b7e2a5c6519a |
| 6.15 | 7.3 | 8740156ad33b |
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
- bpf_cpumask_populate() is a kfunc on BPF_PROG_TYPE_SYSCALL/TRACING/STRUCT_OPS programs loaded via bpf(BPF_PROG_LOAD); the src bitmap is program-local memory, and a SYSCALL program runs it through BPF_PROG_TEST_RUN (bpf_prog_test_run_syscall). Those bits do not arrive in a network protocol message.
- AC:LAttack complexity, low
- A program can call scx_bpf_get_online_cpumask() then bpf_cpumask_populate() in one path; process_kf_arg_ptr_to_btf_id() does not require strict matching here, so the borrowed struct cpumask * is accepted and bitmap_copy() runs with no race or layout dependency.
- PR:LPrivileges required, low
- bpf_prog_load() of BPF_PROG_TYPE_SYSCALL needs only bpf_token_capable(CAP_BPF) (SYSCALL is not in is_perfmon_prog_type); TRACING/STRUCT_OPS also need CAP_PERFMON. bpf_token_capable() checks token->userns, so a delegated BPF token grants this to userns root rather than init-namespace root.
- UI:NUser interaction, none
- The attacker loads their own program and either BPF_PROG_TEST_RUN it or fork() to fire their tp_btf/task_newtask hook; no other user must mount, open a file, or otherwise interact.
- S:UScope, unchanged
- bitmap_copy() overwrites host kernel objects (__cpu_online_mask from scx_bpf_get_online_cpumask(), or task_struct.cpus_mask via cpus_ptr) in the same kernel; this is not a KVM/Xen escape or IOMMU bypass.
- C:NConfidentiality impact, none
- bpf_cpumask_populate() only bitmap_copy()s the caller-supplied src buffer into the destination mask; it does not read kernel memory back to the program or otherwise disclose confidential data.
- I:HIntegrity impact, high
- The destination was typed struct cpumask * rather than struct bpf_cpumask *, so bitmap_copy() writes attacker-controlled bits into borrowed kernel masks such as cpu_online_mask from scx_bpf_get_online_cpumask() or task->cpus_ptr, which bpf_cpumask_set_cpu() would reject.
- A:HAvailability impact, high
- Overwriting writable __cpu_online_mask forges the set walked by for_each_online_cpu(), so the scheduler IPIs or indexes per-CPU state for offline CPUs or sees num_online_cpus()==0, causing a kernel oops or hang.