CVE-2026-47569
Description
A flaw was found in the NVIDIA GPU display driver. A local user can trigger a race condition during handle recycling in the kernel mode layer, resulting in a type confusion condition where memory of one type is misinterpreted as another. A successful exploit could allow an attacker to achieve privilege escalation, execute arbitrary code, access sensitive information, or cause a denial of service (DoS).
Statement
This vulnerability is rated as an Important severity issue because an authenticated local user can exploit kernel-level flaws to gain elevated root privileges or compromise system availability, rather than being remotely reachable. The affected proprietary driver modules are not enabled or installed by default in Red Hat Enterprise Linux, limiting exposure strictly to environments where NVIDIA GPU drivers and specialized hardware have been explicitly deployed for compute or graphical workloads. Multi-tenant systems and workstation deployments that permit unprivileged local user access to NVIDIA device nodes face the greatest operational risk.
Mitigation
To mitigate this vulnerability, prevent the NVIDIA kernel module from loading on systems where GPU acceleration is not strictly required:
1. Create a modprobe configuration file to disable the module:
echo "install nvidia /bin/true" > /etc/modprobe.d/disable-nvidia.conf
2. If the driver is currently loaded, unload it or reboot the system:
reboot
Alternatively, if the GPU is required for workload execution, restrict file permissions on `/dev/nvidia*` device nodes to authorized service accounts or groups only, preventing untrusted local users from interacting directly with the kernel interface.
Warning: Disabling the kernel module requires a system reboot and will disable hardware-accelerated graphics, CUDA, and GPU compute capabilities.
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 | 7.8 | 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 | High | N/A | High |
| Integrity Impact | High | 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:H/I:H/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)
Other
Technical Impact: Varies by Context
When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.
Availability,Integrity,Confidentiality
Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart
If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.