CVE-2026-97496

Received Received - Intake

Memory Corruption in Linux Kernel AMDKFD Driver

Publication date: 2026-09-24

Last updated on: 2026-10-03

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix OOB memory exposure in get_wave_state() The get_wave_state() function for v9 trusts cp_hqd_cntl_stack_size and cp_hqd_cntl_stack_offset values read directly from the MQD, which are written by GPU microcode and fully attacker-controlled on the CRIU-restore path (via AMDKFD_IOC_RESTORE_PROCESS with H3). this leads to an unbounded copy_to_user() that can leak adjacent GTT/kernel memory. If offset > size, integer underflow produces a ~4 GiB read length, if size is set to 1 MiB against a 4 KiB allocation, we leak 1 MiB of adjacent kernel memory (other queues' MQDs, ring buffers, KASLR pointers). Fix by clamping both cp_hqd_cntl_stack_size to the actual allocated buffer size (q->ctl_stack_size) and cp_hqd_cntl_stack_offset to the clamped size before performing arithmetic and copy_to_user(). This ensures we never read beyond the allocated kernel BO regardless of attacker-supplied MQD field values.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-24

Last Modified

2026-10-03

Generated

2026-10-15

AI Q&A

2026-09-25

EPSS Evaluated

2026-10-13

NVD

CVE-2026-97496

EUVD

EUVD-2026-86094

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a memory exposure vulnerability in the Linux kernel's AMDKFD driver. The get_wave_state() function incorrectly trusts values from GPU microcode during CRIU-restore operations. Attackers can manipulate these values to cause an unbounded memory read, leaking adjacent kernel memory including GTT, ring buffers, and KASLR pointers.

Detection Guidance

This vulnerability is specific to the Linux kernel's AMDKFD driver and requires kernel-level access to detect. No direct network detection commands exist. Monitor kernel logs for GPU-related errors or crashes, particularly during CRIU restore operations. Check for unusual memory leaks or kernel memory exposures in AMD GPU driver logs.

Impact Analysis

An attacker with local access could exploit this to read sensitive kernel memory, potentially exposing passwords, encryption keys, or other confidential data. This could lead to privilege escalation or further system compromise.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it pertains to memory exposure in the Linux kernel's AMDKFD driver. However, if exploited, it could lead to unauthorized access to sensitive data, which may violate confidentiality requirements under these regulations depending on the context of use.

Mitigation Strategies

Apply the latest Linux kernel patches that include the fix for CVE-2026-97496. If patching is not immediately possible, restrict access to AMD GPU devices via kernel module blacklisting or system permissions. Avoid using CRIU restore operations on systems with AMD GPUs until patched.

Hi! I’m here to help you understand CVE-2026-97496. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70