CVE-2026-68447

Received Received - Intake

AMDKFD Control Stack Memory Leak in Linux Kernel

Publication date: 2026-08-12

Last updated on: 2026-08-18

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size CRIU checkpoint copies the MQD control stack using cp_hqd_cntl_stack_size from hardware without bounding it to the allocated BO region. If the HW field is larger than the queue's control stack allocation, memcpy reads past the BO into adjacent GTT memory and can leak kernel data to userspace. Store the page-aligned control stack BO size in mqd_manager and clamp checkpoint copies and reported checkpoint sizes to min(cp_hqd_cntl_stack_size, mm->ctl_stack_size). Apply the same bound for multi-XCC v9.4.3 checkpoint layout. (cherry picked from commit 6c2abd0ec09e86c6323010673766f76050e28aa3)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-12

Last Modified

2026-08-18

Generated

2026-09-01

AI Q&A

2026-08-12

EPSS Evaluated

2026-08-31

NVD

CVE-2026-68447

EUVD

EUVD-2026-57053

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	to 9.4.3 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves CRIU (Checkpoint/Restore In Userspace) copying the MQD control stack without properly bounding it to the allocated buffer size. The issue occurs when the hardware field cp_hqd_cntl_stack_size exceeds the actual control stack allocation, causing memcpy to read past the buffer into adjacent memory. This can leak kernel data to userspace.

Detection Guidance

This vulnerability is specific to the Linux kernel's drm/amdkfd driver and involves improper memory handling during CRIU checkpoint operations. Detection requires checking kernel logs for memory corruption or unauthorized access events related to the amdkfd driver. No direct network detection commands are applicable.

Impact Analysis

An attacker with local access could exploit this flaw to read sensitive kernel memory, potentially exposing confidential data or enabling further system compromise. This may lead to information disclosure or privilege escalation on affected systems.

Compliance Impact

This vulnerability could violate compliance requirements under GDPR and HIPAA by enabling unauthorized access to sensitive data. GDPR mandates protection of personal data, while HIPAA requires safeguarding protected health information. Exploitation may result in data breaches, leading to regulatory penalties.

Mitigation Strategies

Apply the latest kernel patches that include the fix for this issue. Monitor for unusual memory access patterns in the amdkfd driver. Restrict untrusted users from accessing GPU-related features if not required.

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

0/70