Linux
bpf: Fix percpu map update indexing with sparse CPU IDs
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360, < c16c62c91e5d6737a9fbb0a541b8b34610470a2b
- >= 8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360, < 75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7
Fixed in c16c62c91e5d6737a9fbb0a541b8b34610470a2b, 75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7
- 7.0
Fixed in 0, 7.2.7, 7.3
Mitigation
Upgrade Linux to c16c62c91e5d6737a9fbb0a541b8b34610470a2b or 75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7 or later.
Upgrade Linux to 0 or 7.2.7 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.