CVE-2026-80883
Description
A flaw was found in the Linux kernel's Tegra graphics driver (drm/tegra: gr2d/gr3d). The host1x_client_register() function is called before the address register map is fully initialized, making the device available to userspace prematurely. This timing issue could allow a local user to submit a job before the register map is ready, potentially leading to system instability or a denial of service (DoS).
Statement
A race in the Tegra DRM gr2d/gr3d probe path can expose the HOST1X client to userspace before the address register map is initialized. A local process may then submit a GPU job during this small window while address register validation state is incomplete. For the CVSS the PR:L is used because triggering requires local access to the Tegra DRM or host1x userspace interface, not administrator privileges in the paranoid interpretation. The issue is not network reachable and is limited to systems using the affected Tegra DRM engines. Impact is at least local denial of service, and in the worst case may include confidentiality or integrity impact if an early job can program GPU address registers before the normal address validation data is ready.
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 | 4.7 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | 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:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
The resource might be left in an unexpected state when it is accessed or used.
Confidentiality
Technical Impact: Read Memory; Read Application Data
When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.
Access Control
Technical Impact: Bypass Protection Mechanism
If security-critical decisions rely on a variable having a "0" or equivalent value, and the programming language performs this initialization on behalf of the programmer, then a bypass of security may occur.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The uninitialized data may contain values that cause program flow to change in ways that the programmer did not intend. For example, if an uninitialized variable is used as an array index in C, then its previous contents may produce an index that is outside the range of the array, possibly causing a crash or an exit in other environments.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.