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

> A local attacker with CAP_CHECKPOINT_RESTORE privileges can trigger a kernel NULL pointer dereference and panic the system via crafted CRIU queue restore operations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89807, DEBIAN-CVE-2026-89807, GHSA-4j65-qcr2-qw3x, UBUNTU-CVE-2026-89807

## What is CVE-2026-89807?

CVE-2026-89807 is a vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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().

## Which versions are affected by CVE-2026-89807?


## How do I fix CVE-2026-89807?

Apply the vendor's patch.

## Is CVE-2026-89807 being exploited?

There is no known exploitation of CVE-2026-89807 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89807 and fix it if it is affected.

What it is: CVE-2026-89807 is a vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89807 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89807/ (Markdown: https://insights.sbomify.com/CVE-2026-89807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89807
- OSV: https://osv.dev/vulnerability/CVE-2026-89807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89807/
Summaries are generated and may contain mistakes; the official description above is the record.