| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025091858-CVE-2023-53388-657a@gregkh> Date: Thu, 18 Sep 2025 15:34:33 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53388: drm/mediatek: Clean dangling pointer on bind error path From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the private object, and that pointer would be passed along to DRM in mtk_drm_sys_prepare() if a suspend were triggered at that point, resulting in a panic. Clean the pointer when destroying the object in the error path to prevent this from happening. The Linux kernel CVE team has assigned CVE-2023-53388 to this issue. Affected and fixed versions =========================== Issue introduced in 4.7 with commit 119f5173628aa7a0c3cf9db83460d40709e8241d and fixed in 4.19.276 with commit 9a48f99aa7bea15e0b1d8b0040c46b4792eddf3b Issue introduced in 4.7 with commit 119f5173628aa7a0c3cf9db83460d40709e8241d and fixed in 5.4.235 with commit a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5 Issue introduced in 4.7 with commit 119f5173628aa7a0c3cf9db83460d40709e8241d and fixed in 5.10.173 with commit 6a89ddee1686a8872384aaa9f0bcfa6b675acd86 Issue introduced in 4.7 with commit 119f5173628aa7a0c3cf9db83460d40709e8241d and fixed in 5.15.99 with commit 49cf87919daeeeeeb9e924c39bdd9203af434461 Issue introduced in 4.7 with commit 119f5173628aa7a0c3cf9db83460d40709e8241d and fixed in 6.1.16 with commit 7b551a501fa714890e55bae73efede1185728d72 Issue introduced in 4.7 with commit 119f5173628aa7a0c3cf9db83460d40709e8241d and fixed in 6.2.3 with commit f3887c771576c5d740c5c5b8bf654a8ab8020b7d Issue introduced in 4.7 with commit 119f5173628aa7a0c3cf9db83460d40709e8241d and fixed in 6.3 with commit 36aa8c61af55675ed967900fbe5deb32d776f051 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-53388 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/mediatek/mtk_drm_drv.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/9a48f99aa7bea15e0b1d8b0040c46b4792eddf3b https://git.kernel.org/stable/c/a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5 https://git.kernel.org/stable/c/6a89ddee1686a8872384aaa9f0bcfa6b675acd86 https://git.kernel.org/stable/c/49cf87919daeeeeeb9e924c39bdd9203af434461 https://git.kernel.org/stable/c/7b551a501fa714890e55bae73efede1185728d72 https://git.kernel.org/stable/c/f3887c771576c5d740c5c5b8bf654a8ab8020b7d https://git.kernel.org/stable/c/36aa8c61af55675ed967900fbe5deb32d776f051
Powered by blists - more mailing lists