# CVE-2026-68364: drm/amd/display: Fix ISM dc_lock deadlock during suspend

> A deadlock in the AMD display driver during suspend can cause a system hang, requiring local access and active video playback to trigger.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-68364, GHSA-3rg2-hc7q-mw7h, UBUNTU-CVE-2026-68364

## What is CVE-2026-68364?

CVE-2026-68364 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, and only if a user opens a file or follows a link.

### Official description

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

drm/amd/display: Fix ISM dc_lock deadlock during suspend

[Why]
System hang observed during suspend/resume while video is playing.
amdgpu_dm_ism_disable() is called under dc_lock and waits for ISM
delayed work via disable_delayed_work_sync(). The work handlers
themselves take dc_lock, producing an ABBA deadlock when a worker is
in flight at suspend time.

[How]
Split the disable path into two phases with opposite locking
contracts:
  1. amdgpu_dm_ism_disable() -- quiesces workers, must NOT hold
     dc_lock.
  2. amdgpu_dm_ism_force_full_power() (new) -- drives the ISM FSM
     back to FULL_POWER_RUNNING, must hold dc_lock.

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


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

Apply the vendor's patch.

## Is CVE-2026-68364 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68364 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-68364 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-68364/ (Markdown: https://insights.sbomify.com/CVE-2026-68364/index.md)
```

## Sources

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

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