| 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: <2025100114-CVE-2023-53484-d863@gregkh> Date: Wed, 1 Oct 2025 13:42:54 +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-53484: lib: cpu_rmap: Avoid use after free on rmap->obj array entries From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: lib: cpu_rmap: Avoid use after free on rmap->obj array entries When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free. Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap(). The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don't hit and issue. Subsequent patches in this series excersize this flow, hence the required fix. The Linux kernel CVE team has assigned CVE-2023-53484 to this issue. Affected and fixed versions =========================== Fixed in 4.14.316 with commit 981f339d2905b6a92ef59358158b326493aecac5 Fixed in 4.19.284 with commit d1308bd0b24cb1d78fa2747d5fa3e055cc628a48 Fixed in 5.4.244 with commit cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000 Fixed in 5.10.181 with commit f748e15253833b771acbede14ea98f50831ac289 Fixed in 5.15.113 with commit c6ed54dd90698dc0744d669524cc1c122ded8a16 Fixed in 6.1.30 with commit c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4 Fixed in 6.3.4 with commit 67bca5f1d644f4e79b694abd8052a177de81c37f Fixed in 6.4 with commit 4e0473f1060aa49621d40a113afde24818101d37 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-53484 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: lib/cpu_rmap.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/981f339d2905b6a92ef59358158b326493aecac5 https://git.kernel.org/stable/c/d1308bd0b24cb1d78fa2747d5fa3e055cc628a48 https://git.kernel.org/stable/c/cc2d2b3dbfb0ba57bc027fb7e1121250c50e4000 https://git.kernel.org/stable/c/f748e15253833b771acbede14ea98f50831ac289 https://git.kernel.org/stable/c/c6ed54dd90698dc0744d669524cc1c122ded8a16 https://git.kernel.org/stable/c/c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4 https://git.kernel.org/stable/c/67bca5f1d644f4e79b694abd8052a177de81c37f https://git.kernel.org/stable/c/4e0473f1060aa49621d40a113afde24818101d37
Powered by blists - more mailing lists