| 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: <2025091516-CVE-2023-53238-f8a7@gregkh> Date: Mon, 15 Sep 2025 16:22:12 +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-53238: phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: phy: hisilicon: Fix an out of bounds check in hisi_inno_phy_probe() The size of array 'priv->ports[]' is INNO_PHY_PORT_NUM. In the for loop, 'i' is used as the index for array 'priv->ports[]' with a check (i > INNO_PHY_PORT_NUM) which indicates that INNO_PHY_PORT_NUM is allowed value for 'i' in the same loop. This > comparison needs to be changed to >=, otherwise it potentially leads to an out of bounds write on the next iteration through the loop The Linux kernel CVE team has assigned CVE-2023-53238 to this issue. Affected and fixed versions =========================== Issue introduced in 4.17 with commit ba8b0ee81fbbc249e60f84bf097bd56e8047c742 and fixed in 4.19.291 with commit 2843a2e703f5cb85c9eeca11b7ee90861635a010 Issue introduced in 4.17 with commit ba8b0ee81fbbc249e60f84bf097bd56e8047c742 and fixed in 5.4.253 with commit 195e806b2afb0bad6470c9094f7e45e0cf109ee0 Issue introduced in 4.17 with commit ba8b0ee81fbbc249e60f84bf097bd56e8047c742 and fixed in 5.10.190 with commit ad249aa3c38f329f91fba8b4b3cd087e79fb0ce8 Issue introduced in 4.17 with commit ba8b0ee81fbbc249e60f84bf097bd56e8047c742 and fixed in 5.15.124 with commit 6d8a71e4c3a2fa4960cc50996e76a42b62fab677 Issue introduced in 4.17 with commit ba8b0ee81fbbc249e60f84bf097bd56e8047c742 and fixed in 6.1.43 with commit 01cb355bb92e8fcf8306e11a4774d610c5864e39 Issue introduced in 4.17 with commit ba8b0ee81fbbc249e60f84bf097bd56e8047c742 and fixed in 6.4.8 with commit ce69eac840db0b559994dc4290fce3d7c0d7bccd Issue introduced in 4.17 with commit ba8b0ee81fbbc249e60f84bf097bd56e8047c742 and fixed in 6.5 with commit 13c088cf3657d70893d75cf116be937f1509cc0f 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-53238 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/phy/hisilicon/phy-hisi-inno-usb2.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/2843a2e703f5cb85c9eeca11b7ee90861635a010 https://git.kernel.org/stable/c/195e806b2afb0bad6470c9094f7e45e0cf109ee0 https://git.kernel.org/stable/c/ad249aa3c38f329f91fba8b4b3cd087e79fb0ce8 https://git.kernel.org/stable/c/6d8a71e4c3a2fa4960cc50996e76a42b62fab677 https://git.kernel.org/stable/c/01cb355bb92e8fcf8306e11a4774d610c5864e39 https://git.kernel.org/stable/c/ce69eac840db0b559994dc4290fce3d7c0d7bccd https://git.kernel.org/stable/c/13c088cf3657d70893d75cf116be937f1509cc0f
Powered by blists - more mailing lists