CVE-2026-80663

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.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: 7.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:

tools/power/x86/intel-speed-select: Harden daemon pidfile open

Avoid symlink-based pidfile clobbering by opening the pidfile with O_NOFOLLOW and validating it with fstat() before locking/writing.

The daemon currently uses a fixed pidfile path under /tmp. A local unprivileged user can pre-create a symlink at that path and cause a root-run daemon instance to write into an attacker-chosen file.

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

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (6)

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

tools/power/x86/intel-speed-select: Harden daemon pidfile open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/607af438e6430893a822964c841a1994b33acccc
generic

tools/power/x86/intel-speed-select: Harden daemon pidfile open - kernel/git/stable/linux.git - Linux kernel stable tree

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

tools/power/x86/intel-speed-select: Harden daemon pidfile open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19ffeb30fdfce63f8d6aca71bcdddb3f69d46278
generic

tools/power/x86/intel-speed-select: Harden daemon pidfile open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72a07abc6b9046f07a08bba353cad7667bcc9dce
generic

tools/power/x86/intel-speed-select: Harden daemon pidfile open - kernel/git/stable/linux.git - Linux kernel stable tree

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

tools/power/x86/intel-speed-select: Harden daemon pidfile open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/905493a6338c82a70da16f86e0a6215db5a3d73d

Vendor Advisories for CVE-2026-80663(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 12× in last 7d / 12× 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 01:22 UTCEPSS rescore
  2. 2026-08-29 19:23 UTCEG score recompute
  3. 2026-08-29 19:23 UTCGHSA enrichment
  4. 2026-08-29 07:26 UTCEG score recompute
  5. 2026-08-29 07:26 UTCGHSA enrichment
  6. 2026-08-29 06:36 UTCEG score recompute 7.10
  7. 2026-08-29 06:36 UTCGHSA enrichment
  8. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:20 UTCNVD update
  11. 2026-08-28 07:34 UTCEG score recompute
  12. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80663?
CVE-2026-80663 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: tools/power/x86/intel-speed-select: Harden daemon pidfile open Avoid symlink-based pidfile clobbering by opening the pidfile with O_NOFOLLOW and validating it with fstat() before locking/writing. The daemon currently uses a fixed…
When was CVE-2026-80663 disclosed?
CVE-2026-80663 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-80663 actively exploited?
CVE-2026-80663 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-80663?
CVE-2026-80663 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-80663?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80663, 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-80663

Explore →

Is Your Infrastructure Affected by CVE-2026-80663?

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