| 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: <2025120947-CVE-2022-50672-d9b1@gregkh> Date: Tue, 9 Dec 2025 10:30:57 +0900 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2022-50672: mailbox: zynq-ipi: fix error handling while device_register() fails From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: mailbox: zynq-ipi: fix error handling while device_register() fails If device_register() fails, it has two issues: 1. The name allocated by dev_set_name() is leaked. 2. The parent of device is not NULL, device_unregister() is called in zynqmp_ipi_free_mboxes(), it will lead a kernel crash because of removing not added device. Call put_device() to give up the reference, so the name is freed in kobject_cleanup(). Add device registered check in zynqmp_ipi_free_mboxes() to avoid null-ptr-deref. The Linux kernel CVE team has assigned CVE-2022-50672 to this issue. Affected and fixed versions =========================== Issue introduced in 5.1 with commit 4981b82ba2ff87df6a711fcd7a233c615df5fc79 and fixed in 5.4.229 with commit b3a5c76f61e2b380e29dfc6705854ca1ee85501d Issue introduced in 5.1 with commit 4981b82ba2ff87df6a711fcd7a233c615df5fc79 and fixed in 5.10.163 with commit a39b4de0804f9fe0ae911b359ffd4afe7d9d933b Issue introduced in 5.1 with commit 4981b82ba2ff87df6a711fcd7a233c615df5fc79 and fixed in 5.15.86 with commit 4f05d8e2fb3ab702c2633a74571e1b31cb579985 Issue introduced in 5.1 with commit 4981b82ba2ff87df6a711fcd7a233c615df5fc79 and fixed in 6.0.16 with commit f2d63cefc012cafe1b7651bbf3302f8bcd8bea4a Issue introduced in 5.1 with commit 4981b82ba2ff87df6a711fcd7a233c615df5fc79 and fixed in 6.1.2 with commit 3fcf079958c00d83c51e4f250abf2c77fe9cc1b9 Issue introduced in 5.1 with commit 4981b82ba2ff87df6a711fcd7a233c615df5fc79 and fixed in 6.2 with commit a6792a0cdef0b1c2d77920246283a72537e60e94 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-2022-50672 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/mailbox/zynqmp-ipi-mailbox.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/b3a5c76f61e2b380e29dfc6705854ca1ee85501d https://git.kernel.org/stable/c/a39b4de0804f9fe0ae911b359ffd4afe7d9d933b https://git.kernel.org/stable/c/4f05d8e2fb3ab702c2633a74571e1b31cb579985 https://git.kernel.org/stable/c/f2d63cefc012cafe1b7651bbf3302f8bcd8bea4a https://git.kernel.org/stable/c/3fcf079958c00d83c51e4f250abf2c77fe9cc1b9 https://git.kernel.org/stable/c/a6792a0cdef0b1c2d77920246283a72537e60e94
Powered by blists - more mailing lists