# CVE-2026-68447: drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size

> A local attacker can leak kernel data to userspace by triggering a CRIU checkpoint copy that reads past the allocated buffer in the AMD KFD driver.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-95519, BELL-CVE-2026-68447, DEBIAN-CVE-2026-68447, GHSA-m433-x9mx-qcj6, UBUNTU-CVE-2026-68447

## What is CVE-2026-68447?

CVE-2026-68447 is a high-severity vulnerability in Linux, published on 12 Aug 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: clamp v9 CRIU control stack checkpoint copy to BO size

CRIU checkpoint copies the MQD control stack using cp_hqd_cntl_stack_size
from hardware without bounding it to the allocated BO region. If the HW
field is larger than the queue's control stack allocation, memcpy reads
past the BO into adjacent GTT memory and can leak kernel data to userspace.

Store the page-aligned control stack BO size in mqd_manager and clamp
checkpoint copies and reported checkpoint sizes to
min(cp_hqd_cntl_stack_size, mm->ctl_stack_size). Apply the same bound
for multi-XCC v9.4.3 checkpoint layout.

(cherry picked from commit 6c2abd0ec09e86c6323010673766f76050e28aa3)

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-68447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68447 is a high-severity vulnerability in Linux, published on 12 Aug 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-68447 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-68447/ (Markdown: https://insights.sbomify.com/CVE-2026-68447/index.md)
```

## Sources

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

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