CVE-2026-74451
Description
A flaw was found in the drm/panthor component of the Linux kernel. The iface_fw_to_cpu_addr() function, responsible for validating firmware interface structure sizes, does not adequately check if the firmware-provided Microcontroller Unit (MCU) virtual address fits entirely within the shared memory section. This oversight allows an address near the end of the shared section to be accepted, potentially leading to out-of-bounds memory accesses. Such accesses could result in system instability or information disclosure.
Statement
The panthor firmware interface code validated only that a firmware provided MCU virtual address started inside the shared section. If the address points near the end of that section, the returned CPU pointer can still be used as a full interface structure and later field accesses may go out-of-bounds. This is a local GPU driver issue and is not network reachable. For the CVSS the PR:L is used for the paranoid score because some deployments may expose GPU render nodes or firmware mediated GPU control to non root local users, even though reliable control of the firmware interface is not proven. Impact is at least denial of service via invalid kernel memory access and in worst case may allow confidentiality or integrity impact because the bug class is out-of-bounds access in kernel memory.
Mitigation
Mitigation for this issue is either not available or the currently available options don't 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 | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| 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:L/UI:N/S:U/C:H/I:H/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.