# CVE-2026-80593: hwmon: (asus_atk0110) Check package count before accessing element

> A missing check in the asus_atk0110 kernel driver allows an out-of-bounds read via malformed firmware, potentially causing a system crash.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-80593, DEBIAN-CVE-2026-80593, GHSA-38hv-9295-2cxw, UBUNTU-CVE-2026-80593

## What is CVE-2026-80593?

CVE-2026-80593 is a high-severity vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-80593?


## How do I fix CVE-2026-80593?

Apply the vendor's patch.

## Is CVE-2026-80593 being exploited?

There is no known exploitation of CVE-2026-80593 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80593 and fix it if it is affected.

What it is: CVE-2026-80593 is a high-severity vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80593 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80593/ (Markdown: https://insights.sbomify.com/CVE-2026-80593/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80593
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80593
- OSV: https://osv.dev/vulnerability/CVE-2026-80593

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80593/
Summaries are generated and may contain mistakes; the official description above is the record.