{"api_version":"1","generated_at":"2026-09-26T13:26:28+00:00","cve":"CVE-2026-98149","urls":{"html":"https://cve.report/CVE-2026-98149","api":"https://cve.report/api/cve/CVE-2026-98149.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98149","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98149"},"summary":{"title":"bpf: Fix percpu map update indexing with sparse CPU IDs","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix percpu map update indexing with sparse CPU IDs\n\nPer-CPU array, hash, and cgroup storage map updates without BPF_F_CPU\nor BPF_F_ALL_CPUS use a value buffer whose per-CPU slots are packed in\npossible-CPU order. The buffer is sized as:\n\n  round_up(value_size, 8) * num_possible_cpus()\n\nThe update paths iterate over possible CPUs, but use the logical CPU ID\nto calculate the source offset:\n\n  value + size * cpu\n\nThis only works when possible CPU IDs are contiguous starting at zero.\n\nFor example, with a possible CPU mask of 0,2-3, the buffer contains\nthree slots corresponding to CPUs 0, 2, and 3. CPU2 is therefore\nexpected to use slot 1 and CPU3 slot 2. Instead, the current code uses\nslots 2 and 3 respectively, causing incorrect per-CPU values and an\nout-of-bounds read from the update buffer for CPU3.\n\nThe corresponding lookup paths already use a dense offset while\niterating over possible CPUs. Do the same for the array, hash, and\ncgroup storage update paths, advancing the source offset once for each\npossible CPU. BPF_F_ALL_CPUS continues to use the same value for every\nCPU.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:46","updated_at":"2026-09-25 11:17:46"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/c16c62c91e5d6737a9fbb0a541b8b34610470a2b","name":"https://git.kernel.org/stable/c/c16c62c91e5d6737a9fbb0a541b8b34610470a2b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7","name":"https://git.kernel.org/stable/c/75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98149","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98149","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360 c16c62c91e5d6737a9fbb0a541b8b34610470a2b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360 75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/bpf/arraymap.c","kernel/bpf/hashtab.c","kernel/bpf/local_storage.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"c16c62c91e5d6737a9fbb0a541b8b34610470a2b","status":"affected","version":"8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360","versionType":"git"},{"lessThan":"75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7","status":"affected","version":"8eb76cb03f0f6c2bd7b15cf45dcffcd6bd07a360","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/bpf/arraymap.c","kernel/bpf/hashtab.c","kernel/bpf/local_storage.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix percpu map update indexing with sparse CPU IDs\n\nPer-CPU array, hash, and cgroup storage map updates without BPF_F_CPU\nor BPF_F_ALL_CPUS use a value buffer whose per-CPU slots are packed in\npossible-CPU order. The buffer is sized as:\n\n  round_up(value_size, 8) * num_possible_cpus()\n\nThe update paths iterate over possible CPUs, but use the logical CPU ID\nto calculate the source offset:\n\n  value + size * cpu\n\nThis only works when possible CPU IDs are contiguous starting at zero.\n\nFor example, with a possible CPU mask of 0,2-3, the buffer contains\nthree slots corresponding to CPUs 0, 2, and 3. CPU2 is therefore\nexpected to use slot 1 and CPU3 slot 2. Instead, the current code uses\nslots 2 and 3 respectively, causing incorrect per-CPU values and an\nout-of-bounds read from the update buffer for CPU3.\n\nThe corresponding lookup paths already use a dense offset while\niterating over possible CPUs. Do the same for the array, hash, and\ncgroup storage update paths, advancing the source offset once for each\npossible CPU. BPF_F_ALL_CPUS continues to use the same value for every\nCPU."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:36:22.182Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/c16c62c91e5d6737a9fbb0a541b8b34610470a2b"},{"url":"https://git.kernel.org/stable/c/75b0a6db4300e4c2c9e97a0848deaa7acfb42fb7"}],"title":"bpf: Fix percpu map update indexing with sparse CPU IDs","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98149","datePublished":"2026-09-25T10:36:22.182Z","dateReserved":"2026-09-25T10:25:14.320Z","dateUpdated":"2026-09-25T10:36:22.182Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:46","lastModifiedDate":"2026-09-25 11:17:46","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98149","Ordinal":"1","Title":"bpf: Fix percpu map update indexing with sparse CPU IDs","CVE":"CVE-2026-98149","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98149","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix percpu map update indexing with sparse CPU IDs\n\nPer-CPU array, hash, and cgroup storage map updates without BPF_F_CPU\nor BPF_F_ALL_CPUS use a value buffer whose per-CPU slots are packed in\npossible-CPU order. The buffer is sized as:\n\n  round_up(value_size, 8) * num_possible_cpus()\n\nThe update paths iterate over possible CPUs, but use the logical CPU ID\nto calculate the source offset:\n\n  value + size * cpu\n\nThis only works when possible CPU IDs are contiguous starting at zero.\n\nFor example, with a possible CPU mask of 0,2-3, the buffer contains\nthree slots corresponding to CPUs 0, 2, and 3. CPU2 is therefore\nexpected to use slot 1 and CPU3 slot 2. Instead, the current code uses\nslots 2 and 3 respectively, causing incorrect per-CPU values and an\nout-of-bounds read from the update buffer for CPU3.\n\nThe corresponding lookup paths already use a dense offset while\niterating over possible CPUs. Do the same for the array, hash, and\ncgroup storage update paths, advancing the source offset once for each\npossible CPU. BPF_F_ALL_CPUS continues to use the same value for every\nCPU.","Type":"Description","Title":"bpf: Fix percpu map update indexing with sparse CPU IDs"}]}}}