# CVE-2026-23051: drm/amdgpu: fix drm panic null pointer when driver not support atomic

> A null pointer dereference in the amdgpu driver causes a kernel panic when atomic support is disabled, leading to local denial of service.

- **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:** 4 Feb 2026
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2026-23051, DEBIAN-CVE-2026-23051, GHSA-g7rw-373x-8c77, UBUNTU-CVE-2026-23051

## What is CVE-2026-23051?

CVE-2026-23051 is a vulnerability in Linux, published on 4 Feb 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: fix drm panic null pointer when driver not support atomic

When driver not support atomic, fb using plane->fb rather than
plane->state->fb.

(cherry picked from commit 2f2a72de673513247cd6fae14e53f6c40c5841ef)

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


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

Apply the vendor's patch.

## Is CVE-2026-23051 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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