[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122423-CVE-2023-54047-42ff@gregkh>
Date: Wed, 24 Dec 2025 13:26:40 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54047: drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
From: Greg Kroah-Hartman <gregkh@...nel.org>
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]
The Linux kernel CVE team has assigned CVE-2023-54047 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.30 with commit 110d4202522373d629d14597af9bac97eb58bd67
Fixed in 6.3.4 with commit 218fe9b624545f4bcfb16cdb35ac3d60c8b0d8c7
Fixed in 6.4 with commit b5af48eedcb53491c02ded55d5991e03d6da6dbf
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-54047
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/110d4202522373d629d14597af9bac97eb58bd67
https://git.kernel.org/stable/c/218fe9b624545f4bcfb16cdb35ac3d60c8b0d8c7
https://git.kernel.org/stable/c/b5af48eedcb53491c02ded55d5991e03d6da6dbf
Powered by blists - more mailing lists