CVE-2026-53076

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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:

  • A CGROUP_STORAGE map is created with value_size not aligned to
8 bytes (e.g., 4 bytes)
  • A pcpu map is created with the same value_size (e.g., 4 bytes)
  • 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.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
1.9%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (5)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

bpf: Fix OOB in pcpu_init_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e19c5ed9f1922a6854073f8651a63fa7be26e9e9
generic

bpf: Fix OOB in pcpu_init_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e0378419b0e20178b5d100b27c9cc7e51064202e
generic

bpf: Fix OOB in pcpu_init_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/634a793d0e1c822412095d25a1338f8831ad894c
generic

bpf: Fix OOB in pcpu_init_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6086079e6d1c32ba4c4b422612b8aebb1129a96c
generic

bpf: Fix OOB in pcpu_init_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/576afddfee8d1108ee299bf10f581593540d1a36

Vendor Advisories for CVE-2026-53076(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 35× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:16 UTCEG score recompute
  2. 2026-07-06 23:16 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:21 UTCEG score recompute
  6. 2026-07-06 11:21 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 22:56 UTCEG score recompute
  10. 2026-07-05 22:56 UTCGHSA enrichment
  11. 2026-07-05 11:02 UTCEG score recompute
  12. 2026-07-05 11:02 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 23:08 UTCEG score recompute
  16. 2026-07-04 23:08 UTCGHSA enrichment
  17. 2026-07-04 11:14 UTCEG score recompute
  18. 2026-07-04 11:14 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-03 23:20 UTCEG score recompute
  21. 2026-07-03 23:20 UTCGHSA enrichment
  22. 2026-07-03 11:25 UTCEG score recompute
  23. 2026-07-03 11:25 UTCGHSA enrichment
  24. 2026-07-02 23:20 UTCEG score recompute
  25. 2026-07-02 23:20 UTCGHSA enrichment
Show 20 more
  1. 2026-07-02 11:27 UTCEG score recompute
  2. 2026-07-02 11:27 UTCGHSA enrichment
  3. 2026-07-01 23:32 UTCEG score recompute
  4. 2026-07-01 23:32 UTCGHSA enrichment
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-07-01 11:39 UTCEG score recompute
  7. 2026-07-01 11:38 UTCGHSA enrichment
  8. 2026-06-30 23:45 UTCEG score recompute 7.10
  9. 2026-06-30 23:45 UTCGHSA enrichment
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 20:59 UTCEG score recompute
  16. 2026-06-27 20:59 UTCGHSA enrichment
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 18:14 UTCEG score recompute
  20. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53076?
CVE-2026-53076 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix OOB in pcpuinitvalue An out-of-bounds read occurs when copying element from a BPFMAPTYPECGROUPSTORAGE map to another pcpu map with the same value_size that is not rounded up to 8 bytes. The issue happens when: 1. A…
When was CVE-2026-53076 disclosed?
CVE-2026-53076 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53076 actively exploited?
CVE-2026-53076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53076?
CVE-2026-53076 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53076, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53076

Explore →

Is Your Infrastructure Affected by CVE-2026-53076?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.