# CVE-2026-80542: drm/amd/display: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank()

> A local attacker can cause a kernel crash via NULL pointer dereference in the AMD GPU display driver when querying vblank sequences.

- **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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** BELL-CVE-2026-80542, DEBIAN-CVE-2026-80542, UBUNTU-CVE-2026-80542

## What is CVE-2026-80542?

CVE-2026-80542 is a vulnerability in Linux, published on 26 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: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank()

amdgpu_dm_crtc_set_vblank() dereferences acrtc_state->stream when
vblank is enabled/queried from DRM_IOCTL_MODE_CRTC_GET_SEQUENCE before
a stream is attached to it.

BUG: kernel NULL pointer dereference, address: 0000000000000008
RIP: amdgpu_dm_crtc_set_vblank+0x6b/0x4d0 [amdgpu]
Call Trace:
 drm_vblank_enable
 drm_vblank_get
 drm_crtc_get_sequence_ioctl
 drm_ioctl_kernel
 drm_ioctl

Reproduced by running VKCTS with WSI tests enabled on RADV.

Guard the enable path on acrtc_state->stream being non-NULL, matching
the existing checks in this function.

(cherry picked from commit 7b1b31bf6942e6f43509b48da23f8e27269aac39)

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


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

Apply the vendor's patch.

## Is CVE-2026-80542 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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