CVE-2026-98149
Last modified
CVE-2026-98149 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 7.0, < 7.2.7 | — |
| Linux | Linux Kernel | 7.3 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-98149?
How severe is CVE-2026-98149?
How do I fix CVE-2026-98149?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98143In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98144In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98145In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98146In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98147In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98148In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-9815The MagicForm WordPress plugin through 0.1.3 does not proper…6.5
- CVE-2026-98150In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-98151In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98152In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98153In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98154In the Linux kernel, the following vulnerability has been re…7
Are you affected by CVE-2026-98149?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
