---
id: "CVE-2026-98905"
kind: "vulnerability"
aliases: ["CVE-2026-98905"]
title: "Linux kernel: AMD KFD checkpoint restore leaves queue buffers unset"
severity: "unknown"
cvss: null
epss: 0.00206
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["amd-gpu", "infrastructure", "kernel", "linux"]
not_affected_if: ["no-amd-gpu"]
published_at: "2026-10-23T12:18:24+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98905", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-98905", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# Linux kernel: AMD KFD checkpoint restore leaves queue buffers unset

In the Linux kernel's AMD GPU compute driver (amdkfd), the CRIU checkpoint-restore path never fills in the buffer fields of a queue's properties, so later code can dereference null pointers. The sources do not describe an attacker-facing effect beyond this kernel crash risk.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98905
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-98905

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

drm/amdkfd: Properly acquire queue buffers in CRIU restore

When kfd_queue_acquire_buffers() was split off from
set_queue_properties_from_user(), set_queue_properties_from_criu()
was missed. Thus, set_queue_properties_from_criu() is not
filling out the buffer fields of queue_properties, which
can come up when subsequent code expects them to be non-null.

Add the proper call to kfd_queue_acquire_buffers(), and also
use the right cast types in set_queue_properties_from_criu()
(which were missed at the same time)

(cherry picked from commit 88ed96abbbe27b70193544fbc1ee06448c274714)

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_