CVE-2023-54047: drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
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]
Security readout for executives and security teams
Plain-English summary
CVE-2023-54047 is a Linux kernel issue in the Rockchip HDMI display driver. The public description says it can cause a use-after-free crash when the module is removed. No CVSS score, CWE, or exploitation evidence is provided in the source bundle.
Executive priority
Treat this as a targeted Linux kernel stability issue. Prioritize patching where Rockchip display hardware is deployed, but broad emergency response is not supported by the provided evidence.
Technical view
The flaw is in drm/rockchip dw_hdmi unbind handling. The DRM encoder is embedded in rockchip_hdmi, whose component memory can be freed before the main DRM device is destroyed. The fix moves encoder cleanup before container teardown to prevent a use-after-free crash during rmmod.
Likely exposure
Exposure appears limited to Linux systems using affected kernel versions with the Rockchip HDMI DRM driver path. The bundle lists Linux as affected, including versions 4.9, 6.1.30, 6.3.4, and 6.4, but does not provide distribution-specific package status.
Exploitation context
There is no KEV listing and no cited source in the bundle claims active exploitation. The described trigger is a crash during module removal, suggesting operational stability risk rather than confirmed remote compromise risk.
Researcher notes
Evidence is narrow: the bundle describes a use-after-free crash during rmmod and lists upstream stable commits. It does not provide CVSS, CWE, privilege requirements, distribution package mappings, proof of exploitation, or a broader impact analysis.
Mitigation direction
Update to a vendor or stable kernel containing the referenced upstream fixes.
Check Linux distribution advisories for package-specific fixed versions.
Prioritize Rockchip-based systems using the HDMI DRM driver.
Avoid unnecessary module unload operations on affected systems until patched.
Track CVE and kernel stable updates for revised severity details.
Validation and detection
Inventory Linux systems and identify Rockchip-based hardware.
Check running kernel versions against vendor fixed-kernel guidance.
Confirm whether the Rockchip HDMI DRM driver is present or loaded.
Verify the kernel includes one of the referenced stable fixes.
Review logs for DRM or module-removal crashes on relevant systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
description · low confidence lookup
Container behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 12:22 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.