CVE-2026-64008
Description
A flaw was found in the accel/rocket component of the Linux kernel. This vulnerability, a Use-After-Free (UAF), occurs in the rocket_ioctl_create_bo() function. A local attacker could exploit this by triggering a failure in subsequent operations after a Graphics Execution Manager (GEM) handle is created, leading to a dangling pointer to freed memory. This allows the attacker to dereference freed memory, which can result in system instability or potentially lead to privilege escalation.
Statement
This Important-severity use-after-free flaw in the Linux kernel accel/rocket driver does not affect Red Hat Enterprise Linux or Red Hat In-Vehicle OS, because the vulnerable code is not present in the shipped kernel packages. The flaw is in rocket_ioctl_create_bo(), which inserts a Graphics Execution Manager (GEM) handle into the file's IDR via drm_gem_handle_create() before several fallible operations (scatter-gather table allocation, drm_mm node insertion, and IOMMU mapping) have completed. If any of those operations fail, the error path frees the GEM object without removing the handle from the IDR, leaving a dangling handle that points to freed slab memory. A local attacker with access to the rocket DRM accelerator device could then issue a subsequent ioctl (PREP_BO, FINI_BO, or SUBMIT) using the dangling handle, causing drm_gem_object_lookup() to return and dereference the freed memory. This could result in a kernel use-after-free that crashes the system (kernel panic) or potentially leads to privilege escalation. Red Hat rates this flaw with a CVSS 3.1 score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), which is lower than the upstream CVE record score of 7.8, because successful exploitation requires a local attacker to reliably trigger specific allocation failures in the buffer-object creation path.
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 | 7 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | 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:H/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)
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.