# CVE-2026-80658: drm/rockchip: dw_dp: Fix null-ptr-deref in dw_dp_remove()

> A null pointer dereference in the Rockchip DisplayPort driver can cause a kernel crash, leading to 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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BELL-CVE-2026-80658, DEBIAN-CVE-2026-80658, GHSA-7w3c-254r-4wj3, UBUNTU-CVE-2026-80658

## What is CVE-2026-80658?

CVE-2026-80658 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/rockchip: dw_dp: Fix null-ptr-deref in dw_dp_remove()

Attempting to access driver data in the platform driver ->remove()
callback may lead to a null pointer dereference since there is no
guaranty that the component ->bind() callback invoking
platform_set_drvdata() was executed.

A common scenario is when Rockchip DRM driver didn't manage to run
component_bind_all() because of an (unrelated) error causing early
return from rockchip_drm_bind().

Drop the unnecessary call to platform_get_drvdata() and, instead,
reference the target device structure via platform_device.

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


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

Apply the vendor's patch.

## Is CVE-2026-80658 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80658 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-80658 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-80658/ (Markdown: https://insights.sbomify.com/CVE-2026-80658/index.md)
```

## Sources

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

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