| 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: <2025050232-CVE-2023-53124-9900@gregkh> Date: Fri, 2 May 2025 17:56:29 +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-53124: scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() Port is allocated by sas_port_alloc_num() and rphy is allocated by either sas_end_device_alloc() or sas_expander_alloc(), all of which may return NULL. So we need to check the rphy to avoid possible NULL pointer access. If sas_rphy_add() returned with failure, rphy is set to NULL. We would access the rphy in the following lines which would also result NULL pointer access. The Linux kernel CVE team has assigned CVE-2023-53124 to this issue. Affected and fixed versions =========================== Issue introduced in 5.4.229 with commit d60000cb1195a464080b0efb4949daf7594e0020 and fixed in 5.4.238 with commit 090305c36185c0547e4441d4c08f1cf096b32134 Issue introduced in 5.10.163 with commit ce1a69cc85006b494353911b35171da195d79e25 and fixed in 5.10.176 with commit 6f0c2f70d9929208d8427ec72c3ed91e2251e289 Issue introduced in 5.15.86 with commit 6a92129c8f999ff5b122c100ce7f625eb3e98c4b and fixed in 5.15.104 with commit 9937f784a608944107dcc2ba9a9c3333f8330b9e Issue introduced in 6.1.2 with commit d17bca3ddfe507874cb826d32721552da12e741f and fixed in 6.1.21 with commit b5e5bbb3fa5f8412e96c5eda7f4a4af6241d6bd3 Issue introduced in 6.2 with commit 78316e9dfc24906dd474630928ed1d3c562b568e and fixed in 6.2.8 with commit a26c775ccc4cfe46f9b718b51bd24313053c7e0b Issue introduced in 6.2 with commit 78316e9dfc24906dd474630928ed1d3c562b568e and fixed in 6.3 with commit d3c57724f1569311e4b81e98fad0931028b9bdcd Issue introduced in 6.0.16 with commit 6f6768e2fc8638fabdd8802c2ef693d7aef01db1 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-53124 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/scsi/mpt3sas/mpt3sas_transport.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/090305c36185c0547e4441d4c08f1cf096b32134 https://git.kernel.org/stable/c/6f0c2f70d9929208d8427ec72c3ed91e2251e289 https://git.kernel.org/stable/c/9937f784a608944107dcc2ba9a9c3333f8330b9e https://git.kernel.org/stable/c/b5e5bbb3fa5f8412e96c5eda7f4a4af6241d6bd3 https://git.kernel.org/stable/c/a26c775ccc4cfe46f9b718b51bd24313053c7e0b https://git.kernel.org/stable/c/d3c57724f1569311e4b81e98fad0931028b9bdcd
Powered by blists - more mailing lists