CVE-2026-80718

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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:

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk()

In pcpu_create_chunk(), nr_pages is the total contiguous backing allocation, i.e., nr_units * pcpu_unit_pages, but pcpu_chunk_populated() uses it to set chunk->populated, whose size is pcpu_unit_pages, bitmap. Since bit N in chunk->populated means page offset N inside every unit is backed. When nr_units > 1, the function writes beyond chunk->populated. Fix it by using chunk->nr_pages.

It also fixes the global pcpu_nr_empty_pop_pages accounting, since pcpu_balance_free() only iterates up to chunk->nr_pages.

Commit a63d4ac4ab609 ("percpu: make percpu-km set chunk->populated bitmap properly") introduced the bitmap overflow issue. Later, commit b539b87fed37f ("percpu: implmeent pcpu_nr_empty_pop_pages and chunk->nr_populated") added pcpu_nr_empty_pop_pages and caused the accounting issue.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (8)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89b1b79c308818a715e75f28744b70d8940a07c9
generic

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c7fc39bf19abb38a996aaad77b3e3a8f48581c3
generic

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32134cf9211b83bed9076d0739c5906fbea4c763
generic

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01504da375f5b19df195cb1cb1cf1dd184318f97
generic

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fc7da2a052f2825fff785e860e67183f5acaaba
generic

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92c43ac3c2b09eb16162e8144e73c00b7c3e29d6
generic

mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f43d2c1bea280dcdfabaf156c25e7402fb8039f

Vendor Advisories for CVE-2026-80718(1)

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 14× in last 7d / 14× 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-08-30 05:28 UTCEG score recompute
  2. 2026-08-30 05:28 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 18:26 UTCEG score recompute
  5. 2026-08-29 18:26 UTCGHSA enrichment
  6. 2026-08-29 07:25 UTCEG score recompute
  7. 2026-08-29 07:24 UTCGHSA enrichment
  8. 2026-08-29 06:35 UTCEG score recompute 7.80
  9. 2026-08-29 06:35 UTCGHSA enrichment
  10. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 08:20 UTCNVD update
  13. 2026-08-28 07:33 UTCEG score recompute
  14. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80718?
CVE-2026-80718 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/percpu-km: fix bitmap overflow and accounting in pcpucreatechunk() In pcpucreatechunk(), nr_pages is the total contiguous backing allocation, i.e., nrunits * pcpuunitpages, but pcpuchunk_populated() uses it to set…
When was CVE-2026-80718 disclosed?
CVE-2026-80718 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80718 actively exploited?
CVE-2026-80718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-80718?
CVE-2026-80718 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80718, 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-80718

Explore →

Is Your Infrastructure Affected by CVE-2026-80718?

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