CVE-2026-89807
CVE CVE-2026-89807EUVD EUVD-2026-80407Published 2026-09-16T10:30:40.000Z
What the advisory describes
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().
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <c643c229babe2e8efc5eefe60e19d44868a643ff; patch: 7.3-rc1; 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <6aa530642f95d5c48aa336416f94a35e7949b647; patch: 6.12.110; 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <19c73848493ab58e39649700da6de11710a36de1; patch: 7.2.5; 6.11; patch: 6.18.51; 48f0bdf4e38e42b8285622cfcfc7e6e490b1a719 <ebffa44e7a21ead59ac4b4264e8fc2cbb44c4a21
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.