CVE-2026-93809
Description
A flaw was found in the Linux kernel's AMD GPU driver (amdgpu). A local user with administrative privileges could cause a Denial of Service (DoS) by unloading the driver module while callbacks are still scheduled. Because the driver does not wait for pending Read-Copy Update (RCU) callbacks to complete before releasing module memory, the system attempts to execute instructions from freed memory, resulting in a kernel crash.
Statement
A moderate severity flaw was found in the Linux kernel's AMD GPU (amdgpu) driver. The driver's module exit path did not call rcu_barrier() to wait for pending Read-Copy-Update (RCU) callbacks before the module text was freed. A local attacker with administrative privileges (the ability to unload kernel modules, such as CAP_SYS_MODULE) could trigger this flaw by unloading the amdgpu driver module while RCU callbacks queued through call_rcu() were still pending; the kernel would then execute a callback from freed module memory, causing a kernel page fault and crash, resulting in a denial of service. There is no impact to confidentiality or integrity. All currently supported Red Hat products are not affected by this flaw because the vulnerable code is not present in the shipped kernels of Red Hat Enterprise Linux 7, 8, 9, and 10, Red Hat In-Vehicle OS, and OpenShift Container Platform. The only Red Hat stream where this flaw is tracked is Red Hat Enterprise Linux 6 Extended Lifecycle Support (kernel), which is out of support scope, so no fix will be provided for it; the residual risk there is limited to a local denial of service by an already privileged user on out-of-support systems.
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)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.