Look up another CVE · open CVE-2026-80593 in the interactive tracker
CVE-2026-80593
hwmon: (asus_atk0110) Check package count before accessing element
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem drivers/hwmon. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80593 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/hwmon/asus_atk0110.c
- What this is
- ATK0110 HWMON DRIVERMAINTAINERS section matched on drivers/hwmon/asus_atk0110.c · linux-hwmon@vger.kernel.org · Maintained
- Kernel module
- asus_atk0110
Check it on the machine
grep -wE 'CONFIG_HWMON|CONFIG_SENSORS_ATK0110' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w asus_atk0110Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/arm64, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
- trixieMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_HWMON, CONFIG_SENSORS_ATK0110
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-28 (2 months ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.20%, higher than 8.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/hwmon
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.32 | 5.10.261 | 2a137124664a |
| 2.6.32 | 5.15.212 | 459b0a0439ea |
| 2.6.32 | 6.1.178 | 768f20e7bb48 |
| 2.6.32 | 6.6.145 | 76392d35c8df |
| 2.6.32 | 6.12.97 | 981a8a2e3773 |
| 2.6.32 | 6.18.40 | d8d4fa0c4f81 |
| 2.6.32 | 7.1.5 | b770fcfcdced |
| 2.6.32 | 7.2 | e2735b39f044 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- atk_ec_present() runs only during local asus_atk0110 platform-driver probe (boot or module load) when ACPI evaluates the GGRP method; there is no network, wireless, or USB packet path to this hwmon parser on x86 ASUS motherboards.
- AC:LAttack complexity, low
- A GGRP sub-package with package.count==0 deterministically indexes elements[0] past the ACPICA allocation on every probe; no race, heap layout lottery, or other attacker-uncontrollable conditions are required once malformed firmware data is present.
- PR:NPrivileges required, none
- Malformed ACPI GGRP packages are returned by system firmware and parsed automatically during driver probe without Linux authentication or capability checks; a supply-chain or evil-maid compromised ASUS BIOS suffices with no local account or namespace privilege at trigger time.
- UI:NUser interaction, none
- Exploitation requires no victim interaction beyond normal power-on and boot; the vulnerable enumeration executes automatically when the ATK0110 ACPI device probes and does not depend on another user opening files or mounting filesystems.
- S:UScope, unchanged
- The out-of-bounds read and any resulting EC misconfiguration or kernel fault remain within the host kernel and local ASUS firmware context; this is not a VM escape, container breakout, or IOMMU boundary crossing.
- C:HConfidentiality impact, high
- Accessing elements[0] on a zero-count ACPI package performs an out-of-bounds kernel heap read of a full union acpi_object, exposing adjacent slab contents interpreted as type and integer fields rather than a strictly bounded few-byte disclosure.
- I:HIntegrity impact, high
- Heap-adjacent data misread as ATK_EC_ID can make atk_ec_present() succeed and drive atk_ec_ctl()/SITM to enable or disable the embedded controller, giving attacker-influenced hardware state modification beyond a read-only fault.
- A:HAvailability impact, high
- Reading past a zero-length ACPICA package allocation can dereference invalid adjacent memory and oops or panic the kernel during probe, and repeated reboots on affected ASUS systems cause persistent denial of service until firmware or the driver is fixed.