CVE-2026-80593
Description
A flaw was found in the Linux kernel, specifically within the hwmon (hardware monitoring) subsystem's asus_atk0110 driver. This vulnerability occurs because the atk_ec_present() function does not properly check the size of a data package before attempting to read its contents. A local attacker could exploit this by providing a specially crafted firmware package, which could lead to an out-of-bounds read. This could result in information disclosure or potentially cause system instability.
Statement
A low impact out-of-bounds read flaw was found in the Linux kernel hwmon subsystem's asus_atk0110 driver, which is shipped in Red Hat Enterprise Linux (kernel and kernel-rt) and Red Hat In-Vehicle OS (kernel and kernel-ivos-qualcomm). The atk_ec_present() function walks the management group package returned by the ACPI GGRP method and reads the first element of each sub-package without first checking that the sub-package is non-empty. A local attacker who can supply a specially crafted ACPI firmware package on affected systems could trigger a read past the end of the allocated element array, resulting in information disclosure or system instability such as a kernel panic. Because triggering the flaw requires malformed ACPI firmware presenting a zero-element sub-package within the ATK0110 management group, and the flaw is limited to a read, the affected components are recorded as affected with the fix deferred to a future scheduled maintenance update; the residual risk until the fix lands is limited to potential information disclosure or a denial of service on hardware whose firmware exposes such malformed packages. Red Hat's severity assessment for this flaw is lower than the upstream CVEORG score of 8.4: an out-of-bounds read of an ACPI package element array does not plausibly yield the high confidentiality and integrity impacts claimed by the upstream vector, and the realistic consequence is primarily availability impact.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 8.4 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.