# CVE-2026-68237: drm/amdgpu/userq: fix indefinite fence wait during GPU reset

> A local attacker can cause a system hang by triggering a GPU reset while a user queue is in a specific state, leading to a denial of service.

- **Severity:** Not scored
- **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:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-68237, GHSA-p526-pm6j-fr73, UBUNTU-CVE-2026-68237

## What is CVE-2026-68237?

CVE-2026-68237 is a denial of service vulnerability in Linux, published on 10 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/amdgpu/userq: fix indefinite fence wait during GPU reset

pre_reset only force-completes fences of MAPPED queues. A queue in any
other state (e.g. mid-eviction) keeps its last_fence pending; after a
GPU reset that fence never signals, so the eviction/suspend worker and
process teardown (amdgpu_evf_mgr_flush_suspend) wait on it forever and
wedge the machine:

  INFO: task kworker/6:28 blocked for more than 120 seconds.
  Workqueue: events amdgpu_eviction_fence_suspend_worker [amdgpu]
  Call Trace:
   dma_fence_wait_timeout+0x7e/0x130
   amdgpu_userq_evict+0x67/0x140 [amdgpu]
   amdgpu_eviction_fence_suspend_worker+0xd8/0x160 [amdgpu]
   process_scheduled_works+0xa6/0x420

Force-complete every queue's fence regardless of state. The unmap and
mark-hung step stays gated on MAPPED, since unmapping a queue that is
not mapped is invalid.

(cherry picked from commit 9102b39fa924dcc3dc75a3137bfa9633c40b88c0)

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


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

Apply the vendor's patch.

## Is CVE-2026-68237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68237 is a denial of service vulnerability in Linux, published on 10 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-68237 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-68237/ (Markdown: https://insights.sbomify.com/CVE-2026-68237/index.md)
```

## Sources

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

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