| 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: <2025091509-CVE-2023-53201-baf1@gregkh> Date: Mon, 15 Sep 2025 16:21:35 +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-53201: RDMA/bnxt_re: wraparound mbox producer index From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: wraparound mbox producer index Driver is not handling the wraparound of the mbox producer index correctly. Currently the wraparound happens once u32 max is reached. Bit 31 of the producer index register is special and should be set only once for the first command. Because the producer index overflow setting bit31 after a long time, FW goes to initialization sequence and this causes FW hang. Fix is to wraparound the mbox producer index once it reaches u16 max. The Linux kernel CVE team has assigned CVE-2023-53201 to this issue. Affected and fixed versions =========================== Issue introduced in 4.11 with commit 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and fixed in 5.10.188 with commit 9341501e2f7af29f5b5562c2840a7fde40eb7de4 Issue introduced in 4.11 with commit 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and fixed in 5.15.121 with commit 79226176cdd1b65a1e6a90e0e1a2b490f0a9df33 Issue introduced in 4.11 with commit 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and fixed in 6.1.39 with commit c9be352be9bb15e6b83e40abc4df7f4776b435ba Issue introduced in 4.11 with commit 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and fixed in 6.3.13 with commit 7bfa0303fbc265c94cfbd17505c55b99848aa4e3 Issue introduced in 4.11 with commit 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and fixed in 6.4.4 with commit 50d77c3739b2b15e9e1f1c9cbe50037d294800f8 Issue introduced in 4.11 with commit 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and fixed in 6.5 with commit 0af91306e17ef3d18e5f100aa58aa787869118af 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-53201 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/infiniband/hw/bnxt_re/qplib_rcfw.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/9341501e2f7af29f5b5562c2840a7fde40eb7de4 https://git.kernel.org/stable/c/79226176cdd1b65a1e6a90e0e1a2b490f0a9df33 https://git.kernel.org/stable/c/c9be352be9bb15e6b83e40abc4df7f4776b435ba https://git.kernel.org/stable/c/7bfa0303fbc265c94cfbd17505c55b99848aa4e3 https://git.kernel.org/stable/c/50d77c3739b2b15e9e1f1c9cbe50037d294800f8 https://git.kernel.org/stable/c/0af91306e17ef3d18e5f100aa58aa787869118af
Powered by blists - more mailing lists