CVE-2026-80671

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.3EG
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.3Exploit: 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 sched: Fix register_pid() overflow, strcpy, and BUG_ON

register_pid() has several issues when processing untrusted perf.data:

  • Integer overflow: (pid + 1) * sizeof(struct task_desc *) can wrap
to a small value on 32-bit systems when pid is large (e.g. 0x40000000), causing realloc to return a tiny buffer followed by out-of-bounds writes in the initialization loop.
  • Heap buffer overflow: strcpy(task->comm, comm) copies the
untrusted comm string into a fixed 20-byte COMM_LEN buffer with no length check.
  • BUG_ON on allocation failure: perf.data is untrusted input, so
allocation failures should be handled gracefully rather than killing the process.
  • Realloc of sched->tasks assigned directly back, leaking the old
pointer on failure; nr_tasks incremented before the realloc, leaving corrupted state on failure.

Cap pid at PID_MAX_LIMIT (4194304, matching the kernel's maximum on 64-bit), replace strcpy with strlcpy, guard against NULL comm, replace BUG_ON with NULL returns using safe realloc patterns, and add NULL checks in callers that dereference the result.

CVSS v3
9.3
EG Score
9.3(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
Severity93% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
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 sched: Fix register_pid() overflow, strcpy, and BUG_ON - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/652cea73b7b7b7c622a2be670e44e3c499c6d49f
generic

perf sched: Fix register_pid() overflow, strcpy, and BUG_ON - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf sched: Fix register_pid() overflow, strcpy, and BUG_ON - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5949d339f5ec98752d56dcd4e36f619a59d513a5

Vendor Advisories for CVE-2026-80671(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 02:18 UTCEG score recompute
  2. 2026-08-30 02:18 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 22:32 UTCGHSA enrichment
  5. 2026-08-29 18:47 UTCGHSA enrichment
  6. 2026-08-29 15:00 UTCGHSA enrichment
  7. 2026-08-29 11:15 UTCEG score recompute
  8. 2026-08-29 11:14 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.30
  12. 2026-08-29 06:36 UTCGHSA enrichment
  13. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 9.3 · 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-80671?
CVE-2026-80671 is a critical vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: perf sched: Fix registerpid() overflow, strcpy, and BUGON register_pid() has several issues when processing untrusted perf.data: 1. Integer overflow: (pid + 1) sizeof(struct task_desc ) can wrap to a small value on 32-bit systems…
When was CVE-2026-80671 disclosed?
CVE-2026-80671 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-80671 actively exploited?
CVE-2026-80671 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 94.9% of all scored CVEs.
What is the CVSS score of CVE-2026-80671?
CVE-2026-80671 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-80671?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80671, 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-80671

Explore →

Is Your Infrastructure Affected by CVE-2026-80671?

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

Start Free Scan →Browse All CVEs