# CVE-2026-98926: drm/amd/display: Remove sink usage from DPMS


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110705, BELL-CVE-2026-98926, DEBIAN-CVE-2026-98926, GHSA-m7h2-h39q-29wg, UBUNTU-CVE-2026-98926

## What is CVE-2026-98926?

CVE-2026-98926 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

drm/amd/display: Remove sink usage from DPMS

[Why]
stream->sink is optional and can be null, so should always be checked
before dereference. Additionally, most of its usage in DPMS sequences
is for stream->sink->link, which can be replaced with stream->link,
as the two should always be the same.

[How]
* Replace stream->sink->link in DPMS on/off
* Add assert to USB4 BW allocation where sink is required
* Avoid inconsistencies in resource access, e.g. don't repeat
stream->link after it was already saved to a local variable
* Pull out effective VPG calculation to helper getter
* Formatting fixes

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


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

Upgrade to a fixed version.

## Is CVE-2026-98926 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98926 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98926 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-98926/ (Markdown: https://insights.sbomify.com/CVE-2026-98926/index.md)
```

## Sources

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

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