drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore (CVE-2026-89807) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89807

drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore

Answer in brief

CVE-2026-89807 records a Unknown severity vulnerability in drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <19c73848493ab58e39649700da6de11710a36de1 \|\| >=48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <ebffa44e7a21ead59ac4b4264e8fc2cbb44c4a21 \|\| >=48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <c643c229babe2e8efc5eefe60e19d44868a643ff \|\| >=48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <6aa530642f95d5c48aa336416f94a35e7949b647	19c73848493ab58e39649700da6de11710a36de1, ebffa44e7a21ead59ac4b4264e8fc2cbb44c4a21, c643c229babe2e8efc5eefe60e19d44868a643ff, 6aa530642f95d5c48aa336416f94a35e7949b647
Linux/Linuxgeneric	6.11	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 19c73848493ab58e39649700da6de11710a36de1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source 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().

Quoted source text, attributed separately from HOL analysis.