# CVE-2026-80705: drm/amd/display: check if dml21_add_phantom_plane() is successful

> A missing check in the AMD display driver can cause a kernel segfault, leading to a local 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:** 28 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-80705, DEBIAN-CVE-2026-80705, GHSA-q2jh-vg55-chvm, UBUNTU-CVE-2026-80705

## What is CVE-2026-80705?

CVE-2026-80705 is a vulnerability in Linux, published on 28 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/amd/display: check if dml21_add_phantom_plane() is successful

Verify that the phantom plane was allocated to avoid a later
segfault.

(cherry picked from commit 5adb54abe5a8e82cbff7f8806db30a5f4924329f)

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


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

Apply the vendor's patch.

## Is CVE-2026-80705 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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