| 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: <2025100452-CVE-2023-53567-dedf@gregkh> Date: Sat, 4 Oct 2025 17:17:21 +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-53567: spi: qup: Don't skip cleanup in remove's error path From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: spi: qup: Don't skip cleanup in remove's error path Returning early in a platform driver's remove callback is wrong. In this case the dma resources are not released in the error path. this is never retried later and so this is a permanent leak. To fix this, only skip hardware disabling if waking the device fails. The Linux kernel CVE team has assigned CVE-2023-53567 to this issue. Affected and fixed versions =========================== Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 4.19.283 with commit fd53f41bd86daa39b454fd4637a908ff2123547f Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 5.4.243 with commit 8632384337038b97910c2f7bb5a3f377aa68d001 Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 5.10.180 with commit bc88243bbe6140d289bb32b4ee4607ba5ce1124a Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 5.15.111 with commit f345d4d71e87d878437417ffbb9a7d4e16d235eb Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 6.1.28 with commit 2d0f63077f481f11a07f20eab1c1f4367dfaef32 Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 6.2.15 with commit 55ecdcd12bc176b86fecbcb125ac814ac8fe857a Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 6.3.2 with commit 49c17fccae36505550c9121891722fff337f148a Issue introduced in 3.15 with commit 64ff247a978facc437d40f0c9b754675846a98f0 and fixed in 6.4 with commit 61f49171a43ab1f80c73c5c88c508770c461e0f2 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-53567 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/spi/spi-qup.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/fd53f41bd86daa39b454fd4637a908ff2123547f https://git.kernel.org/stable/c/8632384337038b97910c2f7bb5a3f377aa68d001 https://git.kernel.org/stable/c/bc88243bbe6140d289bb32b4ee4607ba5ce1124a https://git.kernel.org/stable/c/f345d4d71e87d878437417ffbb9a7d4e16d235eb https://git.kernel.org/stable/c/2d0f63077f481f11a07f20eab1c1f4367dfaef32 https://git.kernel.org/stable/c/55ecdcd12bc176b86fecbcb125ac814ac8fe857a https://git.kernel.org/stable/c/49c17fccae36505550c9121891722fff337f148a https://git.kernel.org/stable/c/61f49171a43ab1f80c73c5c88c508770c461e0f2
Powered by blists - more mailing lists