CVE-2026-80593

HIGHPre-NVD 8.48.4
EchelonGraph scoreHIGH confidence

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

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

hwmon: (asus_atk0110) Check package count before accessing element

atk_ec_present() walks the management group package returned by the GGRP ACPI method and, for each sub-package, reads its first element:

id = &obj->package.elements[0]; if (id->type != ACPI_TYPE_INTEGER)

without checking that the sub-package is non-empty. ACPICA allocates the element array with exactly package.count entries, so for a sub-package with a zero count this reads past the allocation.

The sibling function atk_debugfs_ggrp_open() performs the same access but skips empty packages with a package.count check first. Add the same check to atk_ec_present() so a malformed firmware package cannot trigger an out-of-bounds read.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
42(Track)
EG Risk 42/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
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
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

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/981a8a2e3773dc7e704943388a1fb97970b23275
generic

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76392d35c8df471b288cfc6536bd092b3c8ee2cf
generic

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/768f20e7bb48d723b82cb142120263d0806fbeb8
generic

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/459b0a0439ea65b2b612aa572eb62a2e26d05618
generic

hwmon: (asus_atk0110) Check package count before accessing element - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a137124664aad1e36d8d74e8e2207365a04737f

Vendor Advisories for CVE-2026-80593(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 18:41 UTCEG score recompute
  3. 2026-08-29 18:41 UTCGHSA enrichment
  4. 2026-08-29 07:27 UTCEG score recompute
  5. 2026-08-29 07:27 UTCGHSA enrichment
  6. 2026-08-29 06:37 UTCEG score recompute 8.40
  7. 2026-08-29 06:37 UTCGHSA enrichment
  8. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:20 UTCNVD update
  11. 2026-08-28 07:38 UTCEG score recompute
  12. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80593?
CVE-2026-80593 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: (asus_atk0110) Check package count before accessing element atkecpresent() walks the management group package returned by the GGRP ACPI method and, for each sub-package, reads its first element: id =…
When was CVE-2026-80593 disclosed?
CVE-2026-80593 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-80593 actively exploited?
CVE-2026-80593 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 96.0% of all scored CVEs.
What is the CVSS score of CVE-2026-80593?
CVE-2026-80593 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-80593?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80593, 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-80593

Explore →

Is Your Infrastructure Affected by CVE-2026-80593?

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