CVE-2026-53076: Linux kernel · bpf: Fix OOB in pcpu_init_value
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in e0378419b0e20178b5d100b27c9cc7e51064202e : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:07 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in e0378419b0e20178b5d100b27c9cc7e51064202e, e19c5ed9f1922a6854073f8651a63fa7be26e9e9, 6086079e6d1c32ba4c4b422612b8aebb1129a96c +4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/e19c5ed9f1922a6854073f8651a63fa7be26e9e9 (opens in a new tab)
- git.kernel.org/stable/c/e0378419b0e20178b5d100b27c9cc7e51064202e (opens in a new tab)
- git.kernel.org/stable/c/6086079e6d1c32ba4c4b422612b8aebb1129a96c (opens in a new tab)
- git.kernel.org/stable/c/634a793d0e1c822412095d25a1338f8831ad894c (opens in a new tab)
- git.kernel.org/stable/c/576afddfee8d1108ee299bf10f581593540d1a36 (opens in a new tab)