CVE-2026-89438
Description
A flaw was found in the Linux kernel, specifically within the Intel Speed Select Technology (ISST) component. This vulnerability arises from insufficient validation of input values, such as logical CPU ID and CLOS ID, used in the core power feature. A local attacker could exploit this by providing invalid input, which might lead to incorrect calculations for memory-mapped I/O (MMIO) offsets. This could result in memory corruption, potentially allowing for system instability, unauthorized information access, or an increase in privileges.
Statement
A MODERATE severity flaw was found in the Linux kernel's Intel Speed Select Technology (ISST) driver, affecting the kernel packages that Red Hat ships in Red Hat Enterprise Linux 9 and 10 and in the RHEL CoreOS kernels used by OpenShift Container Platform 4.16 and later. The ISST core power feature fails to validate the logical CPU ID and CLOS ID supplied by userspace before using those values to calculate a memory-mapped I/O (MMIO) offset. A local attacker with sufficient privileges to access the ISST interface could submit out-of-range logical CPU or CLOS IDs, causing an out-of-bounds write and kernel memory corruption, which could result in a system crash or denial of service, and potentially in information disclosure or privilege escalation. Red Hat rated this flaw MODERATE (CVSS 5.5, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because exploitation requires local access with privileges and the primary impact is to system availability. Red Hat Enterprise Linux 6, 7, and 8, and OpenShift Container Platform 4.12 through 4.15, are not affected because the vulnerable code is not present in the kernel versions they ship. For the affected Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, and OpenShift Container Platform 4.16 and later streams, the fix is deferred because the flaw is MODERATE severity with a CVSS score below 7.0, below the threshold at which Red Hat prioritizes filing fixes for this component. The residual risk is that a privileged local user on an affected system could trigger kernel memory corruption or a denial of service.
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 | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce 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.