| 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: <2025102212-CVE-2023-53704-9f42@gregkh> Date: Wed, 22 Oct 2025 15:24:43 +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-53704: clk: imx: clk-imx8mp: improve error handling in imx8mp_clocks_probe() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: clk: imx: clk-imx8mp: improve error handling in imx8mp_clocks_probe() Replace of_iomap() and kzalloc() with devm_of_iomap() and devm_kzalloc() which can automatically release the related memory when the device or driver is removed or unloaded to avoid potential memory leak. In this case, iounmap(anatop_base) in line 427,433 are removed as manual release is not required. Besides, referring to clk-imx8mq.c, check the return code of of_clk_add_hw_provider, if it returns negtive, print error info and unregister hws, which makes the program more robust. The Linux kernel CVE team has assigned CVE-2023-53704 to this issue. Affected and fixed versions =========================== Issue introduced in 5.6 with commit 9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 and fixed in 5.10.188 with commit cb047c13bbf9018693ae31f03a5a26b212d02f13 Issue introduced in 5.6 with commit 9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 and fixed in 5.15.121 with commit bcea444ab4c045864b55d67313833d606676602a Issue introduced in 5.6 with commit 9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 and fixed in 6.1.39 with commit 6317d0302655f7e854cd4f31e93b47d35cb058bb Issue introduced in 5.6 with commit 9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 and fixed in 6.3.13 with commit 5bcf140e9e6cf76f1f1bd1f489a14ca4d49f9a1a Issue introduced in 5.6 with commit 9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 and fixed in 6.4.4 with commit 92ce7629a11ae62292e1cfaa6132dab081fc80ee Issue introduced in 5.6 with commit 9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 and fixed in 6.5 with commit 878b02d5f3b56cb090dbe2c70c89273be144087f 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-53704 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/clk/imx/clk-imx8mp.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/cb047c13bbf9018693ae31f03a5a26b212d02f13 https://git.kernel.org/stable/c/bcea444ab4c045864b55d67313833d606676602a https://git.kernel.org/stable/c/6317d0302655f7e854cd4f31e93b47d35cb058bb https://git.kernel.org/stable/c/5bcf140e9e6cf76f1f1bd1f489a14ca4d49f9a1a https://git.kernel.org/stable/c/92ce7629a11ae62292e1cfaa6132dab081fc80ee https://git.kernel.org/stable/c/878b02d5f3b56cb090dbe2c70c89273be144087f
Powered by blists - more mailing lists