CVE-2026-65586
Received Received - Intake

Use-After-Free in GPU Driver Leading to Arbitrary Memory Access

Vulnerability report for CVE-2026-65586, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-30

Last updated on: 2026-10-30

Assigner: imaginationtech

Description

Software installed and run as a non-privileged user may conduct improper GPU system calls to free memory in still in use, replace with another allocation and cause arbitrary memory reads or writes to physical memory pages. A memory buffer managed by a CPU thread of control (driver) and accessed by a GPU thread of control (firmware) can be freed while in use. Software installed and run as a non-privileged user may replace that buffer with another and replace a shared resource (memory page address list) managed by the CPU thread of control (driver) leading to the GPU accessing memory not managed by the CPU thread of control (driver).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-30
Last Modified
2026-10-30
Generated
2026-10-30
AI Q&A
2026-10-30
EPSS Evaluated
N/A
NVD
EUVD

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves improper GPU system calls that allow non-privileged users to free memory still in use. The attacker can replace the freed memory with another allocation, leading to arbitrary memory reads or writes to physical memory pages. This occurs because a memory buffer managed by a CPU thread can be freed while a GPU thread is still accessing it, causing the GPU to access unintended memory regions.

Detection Guidance

This vulnerability involves improper GPU memory handling by non-privileged software. Detection requires monitoring GPU driver logs for memory access violations or unexpected buffer replacements. Check for crashes or errors in graphics-related processes using system logs or tools like dmesg on Linux. No specific commands are provided in the context.

Impact Analysis

This vulnerability could allow an attacker with local access to execute arbitrary code, escalate privileges, or crash the system. It may lead to unauthorized data access, system instability, or complete system compromise depending on the affected software and hardware configuration.

Compliance Impact

This vulnerability could lead to arbitrary memory reads or writes, potentially exposing sensitive data. For GDPR, this may violate principles of data protection and confidentiality. For HIPAA, it could compromise protected health information integrity and security.

Mitigation Strategies

Immediate mitigation involves updating the GPU driver to the latest version from the vendor. Restrict non-privileged user access to GPU system calls if possible. Monitor for unusual memory access patterns in GPU-related processes. No specific steps are detailed in the provided context.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-65586. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart