# CVE-2026-98785: drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend

> A null pointer dereference in the Linux kernel AMD display driver during GPU reset recovery can cause a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108822, BELL-CVE-2026-98785, DEBIAN-CVE-2026-98785, GHSA-m7hp-r32v-xxxr, UBUNTU-CVE-2026-98785

## What is CVE-2026-98785?

CVE-2026-98785 is a vulnerability in Linux, published on 18 Oct 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/amd/display: check dc_state_create_copy() for NULL in dm_suspend

dc_state_create_copy() can return NULL on allocation failure.
dm_suspend() only conditionally skips dm_gpureset_toggle_interrupts()
and continues execution, returning success.  dm_resume() then
dereferences the NULL cached_dc_state in link_enc_cfg_copy() and the
following dc_state->stream_count loop, crashing during GPU reset
recovery.

Return -ENOMEM immediately if the copy fails, so the caller aborts
suspend instead of leaving a NULL cached state for resume.

(cherry picked from commit 84b6d7932fdd2857795a257f9f258562a3cddcab)

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


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

Apply the vendor's patch.

## Is CVE-2026-98785 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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