| 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: <2025061805-CVE-2022-50104-38ee@gregkh> Date: Wed, 18 Jun 2025 13:02:49 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2022-50104: powerpc/xive: Fix refcount leak in xive_get_max_prio From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: Fix refcount leak in xive_get_max_prio of_find_node_by_path() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak. The Linux kernel CVE team has assigned CVE-2022-50104 to this issue. Affected and fixed versions =========================== Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 4.14.291 with commit 5ed9709d262bf026b2ff64979fbfe0f496287588 Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 4.19.256 with commit f658d5b528ce97a68efbb64ee54f6fe0909b189a Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.4.211 with commit d99733ad47a6c990b52e136608455643bfa708f2 Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.10.137 with commit 6d1e53f7f181a11a8a343def1e0d0209905b7c64 Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.15.61 with commit ea494e8a9852abd0ba60f69b254ce0d7c38449e2 Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.18.18 with commit 2e18b869a8d574cfe9ee64df9c3d0a7ac7ed07a8 Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.19.2 with commit 79b8eae24b7ee157bda07695d802be8576983fa8 Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 6.0 with commit 255b650cbec6849443ce2e0cdd187fd5e61c218c 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-50104 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: arch/powerpc/sysdev/xive/spapr.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/5ed9709d262bf026b2ff64979fbfe0f496287588 https://git.kernel.org/stable/c/f658d5b528ce97a68efbb64ee54f6fe0909b189a https://git.kernel.org/stable/c/d99733ad47a6c990b52e136608455643bfa708f2 https://git.kernel.org/stable/c/6d1e53f7f181a11a8a343def1e0d0209905b7c64 https://git.kernel.org/stable/c/ea494e8a9852abd0ba60f69b254ce0d7c38449e2 https://git.kernel.org/stable/c/2e18b869a8d574cfe9ee64df9c3d0a7ac7ed07a8 https://git.kernel.org/stable/c/79b8eae24b7ee157bda07695d802be8576983fa8 https://git.kernel.org/stable/c/255b650cbec6849443ce2e0cdd187fd5e61c218c
Powered by blists - more mailing lists