CVE-2026-23116
Description
A flaw was found in the Linux kernel. On i.MX8MQ platforms, the Video Processing Unit (VPU) power management incorrectly attempts to reset or ungate VPU instances independently. This invalid hardware sequence can be triggered by a local user through driver operations, runtime power management, or multimedia usage. Successful exploitation leads to a full system hang, resulting in a local Denial of Service (DoS).
Statement
On i.MX8MQ the VPUMIX domain ADB block does not provide separate reset and clock enable bits per VPU instance. The previous power domain data defined per domain rst_mask and clk_mask values for vpublk g1 and vpublk g2. As a result the kernel could attempt to reset or ungate one VPU independently. That hardware sequence is invalid on i.MX8MQ and can lead to a full system hang. This is an availability issue that can be triggered by local activity that causes VPU power management transitions. Such activity can be reached through driver probe and remove. Runtime PM operations. Or higher level multimedia usage that toggles VPU domains. The patch removes the per domain rst_mask and clk_mask so the generic block control code will not try to reset or clock gate G1 or G2 separately. Instead the existing imx8mq_vpu_power_notifier is relied on to perform the correct combined VPU reset sequence. The main impact is preventing a local denial of service on affected embedded systems.
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 | 5.5 | N/A |
| Attack Vector | Local | Local | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | Low | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU)
Inconsistent locking discipline can lead to deadlock.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
