drm/amdkfd: Check bounds on CRIU restore queue type and mqd size
CVE-2026-68258 · published 10 Aug 2026
How serious is it
- Severity: high, CVSS score 7.1 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-68258?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 42c6c48214b726c30918e8dc80e2168607d13ae4 to < 2b817c0dfc653bf33d0e0ab8155ff7807a617487, 42c6c48214b726c30918e8dc80e2168607d13ae4 to < 1956aa246c65c5895589664ccb37d0710aa8d304, 42c6c48214b726c30918e8dc80e2168607d13ae4 to < fd1691ec62701c982ea32e749678988c67fd4c21, 42c6c48214b726c30918e8dc80e2168607d13ae4 to < cc10a5839756982504ee8568fc1e1625962ab7f8
- Linux Linux: 5.18
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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)
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/2b817c0dfc653bf33d0e0ab8155ff7807a617487
- git.kernel.org/stable/c/1956aa246c65c5895589664ccb37d0710aa8d304
- git.kernel.org/stable/c/fd1691ec62701c982ea32e749678988c67fd4c21
- git.kernel.org/stable/c/cc10a5839756982504ee8568fc1e1625962ab7f8
- git.kernel.org/stable/c/47ea05f246bebc81c7796f56265cffd812cf0601
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON