CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size
Greg Kroah-Hartman <[email protected]>
| Newsgroups | org.kernel.vger.linux-cve-announce |
|---|---|
| Message-ID | <2026081021-CVE-2026-68258-6be3@gregkh> |
From: Greg Kroah-Hartman <[email protected]> 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) The Linux kernel CVE team has assigned CVE-2026-68258 to this issue. Affected and fixed versions =========================== Fixed in 6.18.42 with commit fd1691ec62701c982ea32e749678988c67fd4c21 Fixed in 7.1.6 with commit cc10a5839756982504ee8568fc1e1625962ab7f8 Fixed in 7.2-rc3 with commit 47ea05f246bebc81c7796f56265cffd812cf0601 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-68258 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.h drivers/gpu/drm/amd/amdkfd/kfd_priv.h drivers/gpu/drm/amd/amdkfd/kfd_process_queue_manager.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/fd1691ec62701c982ea32e749678988c67fd4c21 https://git.kernel.org/stable/c/cc10a5839756982504ee8568fc1e1625962ab7f8 https://git.kernel.org/stable/c/47ea05f246bebc81c7796f56265cffd812cf0601