# CVE-2023-54047: drm/rockchip: dw_hdmi: cleanup drm encoder during unbind

> A use-after-free vulnerability in the Rockchip DRM HDMI driver allows local attackers with root privileges to cause a system crash during module unloading.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54047, DEBIAN-CVE-2023-54047, GHSA-mg6p-rh4v-v7jm, ROOT-OS-DEBIAN-11-CVE-2023-54047, ROOT-OS-UBUNTU-2204-CVE-2023-54047, UBUNTU-CVE-2023-54047

## What is CVE-2023-54047?

CVE-2023-54047 is an use after free vulnerability in Linux, published on 24 Dec 2025. 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_hdmi: cleanup drm encoder during unbind

This fixes a use-after-free crash during rmmod.

The DRM encoder is embedded inside the larger rockchip_hdmi,
which is allocated with the component. The component memory
gets freed before the main drm device is destroyed. Fix it
by running encoder cleanup before tearing down its container.

[moved encoder cleanup above clk_disable, similar to bind-error-path]

## Which versions are affected by CVE-2023-54047?


## How do I fix CVE-2023-54047?

Apply the vendor's patch.

## Is CVE-2023-54047 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54047 and fix it if it is affected.

What it is: CVE-2023-54047 is an use after free vulnerability in Linux, published on 24 Dec 2025. 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-2023-54047 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-2023-54047/ (Markdown: https://insights.sbomify.com/CVE-2023-54047/index.md)
```

## Sources

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

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