| 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: <2025061838-CVE-2022-50197-ed69@gregkh> Date: Wed, 18 Jun 2025 13:04:22 +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-50197: cpufreq: zynq: Fix refcount leak in zynq_get_revision From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: cpufreq: zynq: Fix refcount leak in zynq_get_revision of_find_compatible_node() 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-50197 to this issue. Affected and fixed versions =========================== Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 4.14.291 with commit f52c9be1779d70037ae300762d19b08fe3656237 Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 4.19.256 with commit dcbb974254d2a27240c2e50185afdde90f923feb Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 5.4.211 with commit a530fa52d4fdffc5f010f90c05ac63019b8ff5f8 Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 5.10.137 with commit 22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 5.15.61 with commit 179034fb108e3655142f2af0c309cef171c34d68 Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 5.18.18 with commit ecefd22d5db7ccb8bec2646e5d25e058fc33162a Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 5.19.2 with commit 3b01353f1825151a29d08e0868b2bf01e1116ab5 Issue introduced in 3.16 with commit 00f7dc636366f72474b1896f4990b3c086cd2c6d and fixed in 6.0 with commit d1ff2559cef0f6f8d97fba6337b28adb10689e16 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-50197 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/arm/mach-zynq/common.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/f52c9be1779d70037ae300762d19b08fe3656237 https://git.kernel.org/stable/c/dcbb974254d2a27240c2e50185afdde90f923feb https://git.kernel.org/stable/c/a530fa52d4fdffc5f010f90c05ac63019b8ff5f8 https://git.kernel.org/stable/c/22e6d8bcde8e66b64f46bf9bd2d3d0f88d40c39f https://git.kernel.org/stable/c/179034fb108e3655142f2af0c309cef171c34d68 https://git.kernel.org/stable/c/ecefd22d5db7ccb8bec2646e5d25e058fc33162a https://git.kernel.org/stable/c/3b01353f1825151a29d08e0868b2bf01e1116ab5 https://git.kernel.org/stable/c/d1ff2559cef0f6f8d97fba6337b28adb10689e16
Powered by blists - more mailing lists