CVE-2026-80670

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

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

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

perf tools: Use perf_env__get_cpu_topology() in machine__resolve()

machine__resolve() accesses env->cpu[al->cpu].socket_id after checking al->cpu >= 0 and env->cpu != NULL, but without validating al->cpu against env->nr_cpus_avail. Since al->cpu comes from the untrusted perf.data sample, a crafted file with a large CPU index causes an out-of-bounds heap read.

Use perf_env__get_cpu_topology() which validates both NULL and bounds. Also bounds-check al->cpu before the cast to struct perf_cpu (int16_t): without this, values like 65536 silently truncate to 0, bypassing the accessor's internal check and returning CPU 0's topology.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (3)

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

perf tools: Use perf_env__get_cpu_topology() in machine__resolve() - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf tools: Use perf_env__get_cpu_topology() in machine__resolve() - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf tools: Use perf_env__get_cpu_topology() in machine__resolve() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5484b43a0ec8231c36fba6ead654cb72dbba8b8f

Vendor Advisories for CVE-2026-80670(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 17× in last 7d / 17× 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:29 UTCEG score recompute
  2. 2026-08-30 05:29 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-30 01:05 UTCGHSA enrichment
  5. 2026-08-29 20:41 UTCGHSA enrichment
  6. 2026-08-29 16:17 UTCGHSA enrichment
  7. 2026-08-29 11:51 UTCEG score recompute
  8. 2026-08-29 11:51 UTCGHSA enrichment
  9. 2026-08-29 07:26 UTCEG score recompute
  10. 2026-08-29 07:26 UTCGHSA enrichment
  11. 2026-08-29 06:36 UTCEG score recompute▲ 9.10
  12. 2026-08-29 06:36 UTCGHSA enrichment
  13. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-28 08:20 UTCNVD update
  16. 2026-08-28 07:34 UTCEG score recompute
  17. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80670?
CVE-2026-80670 is a critical vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: perf tools: Use perfenvgetcpu_topology() in machineresolve() machineresolve() accesses env->cpu[al->cpu].socket_id after checking al->cpu >= 0 and env->cpu != NULL, but without validating al->cpu against env->nrcpusavail. Since…
When was CVE-2026-80670 disclosed?
CVE-2026-80670 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-80670 actively exploited?
CVE-2026-80670 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 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-80670?
CVE-2026-80670 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-80670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80670, 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-80670

Explore →

Is Your Infrastructure Affected by CVE-2026-80670?

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

Start Free Scan →Browse All CVEs