CVE-2026-98149

published 25 Sep 2026 · updated 19 Oct 2026

bpf: Fix percpu map update indexing with sparse CPU IDs

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7 and Kernel c16c62c91e5d6737a9fbb0a541b8b34610470a2b.

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix percpu map update indexing with sparse CPU IDs Per-CPU array, hash, and cgroup storage map updates without BPF_F_CPU or BPF_F_ALL_CPUS use a value buffer whose per-CPU slots are packed in possible-CPU order. The buffer is sized as: round_up(value_size, 8) * num_possible_cpus() The update paths iterate over possible CPUs, but use the logical CPU ID to calculate the source offset: value + size * cpu This only works when possible CPU IDs are contiguous starting at zero. For example, with a possible CPU mask of 0,2-3, the buffer contains three slots corresponding to CPUs 0, 2, and 3. CPU2 is therefore expected to use slot 1 and CPU3 slot 2. Instead, the current code uses slots 2 and 3 respectively, causing incorrect per-CPU values and an out-of-bounds read from the update buffer for CPU3. The corresponding lookup paths already use a dense offset while iterating over possible CPUs. Do the same for the array, hash, and cgroup storage update paths, advancing the source offset once for each possible CPU. BPF_F_ALL_CPUS continues to use the same value for every CPU.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=7.0, >=8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360 <75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7, >=8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360 <c16c62c91e5d6737a9fbb0a541b8b34610470a2b75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7, c16c62c91e5d6737a9fbb0a541b8b34610470a2b

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98149 severity on Zeptric[![CVE-2026-98149](https://zeptric.io/badge/cve/CVE-2026-98149.svg)](https://zeptric.io/cve/CVE-2026-98149)