Description
In the Linux kernel, the following vulnerability has been resolved:

drm/amdkfd: Check bounds on CRIU restore queue type and mqd size

We weren't checking whether the values provided in the private
data in kfd CRIU restore were within bounds.

For queue type, add a KFD_QUEUE_TYPE_MAX and ensure the provided
type is less than it.

For mqd_size, add new function mqd_size_from_queue_type and confirm
that the provided mqd_size matches expectations.

(cherry picked from commit f19d8086f6644083c913d70bfdeee20e1b6f46a5)
Published: 2026-08-10
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises from missing bounds checks on the queue type and mqd_size values supplied during a CRIU restore in the Linux kernel’s KFD DRM module. Without these validations, an attacker could provide malformed data that leads to undefined kernel behavior, potentially causing memory corruption or a kernel crash. This flaw does not explicitly guarantee privilege escalation, but the kernel-level impact could be leveraged by a skilled adversary to disrupt system operation or gain higher privileges if combined with other weaknesses.

Affected Systems

All Linux kernel builds that include the KFD DRM module prior to the patch are affected; specific version numbers are not listed in the CNA data, so any kernel compiled with this code path before the fix may be vulnerable. The impact applies to the entire Linux kernel operating system.

Risk and Exploitability

The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, indicating no current widespread exploitation. However, the absence of input validation in a critical kernel routine suggests high severity if an attacker can influence CRIU restore parameters. Likely attack vectors involve a local user or privileged process crafting a malicious CRIU restore file; successful exploitation could lead to system instability or potentially enable privilege escalation through subsequent kernel exploitation.

Generated by OpenCVE AI on August 10, 2026 at 17:32 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a release that includes commit f19d8086f6644083c913d70bfdeee20e1b6f46a5
  • If a kernel upgrade is not immediately feasible, unload or disable the KFD DRM module to eliminate the unchecked code path
  • Implement additional input validation for CRIU restore data, such as ensuring queue type values are less than KFD_QUEUE_TYPE_MAX and that mqd_size matches the expected size before proceeding with the restore

Generated by OpenCVE AI on August 10, 2026 at 17:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 18:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-129
CWE-20

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size We weren't checking whether the values provided in the private data in kfd CRIU restore were within bounds. For queue type, add a KFD_QUEUE_TYPE_MAX and ensure the provided type is less than it. For mqd_size, add new function mqd_size_from_queue_type and confirm that the provided mqd_size matches expectations. (cherry picked from commit f19d8086f6644083c913d70bfdeee20e1b6f46a5)
Title drm/amdkfd: Check bounds on CRIU restore queue type and mqd size
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-10T12:01:32.149Z

Reserved: 2026-07-30T09:28:09.378Z

Link: CVE-2026-68258

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T19:30:17Z

Weaknesses
  • CWE-129

    Improper Validation of Array Index

  • CWE-20

    Improper Input Validation