| 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: <2025022625-CVE-2022-49678-d39c@gregkh> Date: Wed, 26 Feb 2025 03:24:01 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49678: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe Description =========== In the Linux kernel, the following vulnerability has been resolved: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. In brcmstb_init_sram, it pass dn to of_address_to_resource(), of_address_to_resource() will call of_find_device_by_node() to take reference, so we should release the reference returned by of_find_matching_node(). The Linux kernel CVE team has assigned CVE-2022-49678 to this issue. Affected and fixed versions =========================== Issue introduced in 4.15 with commit 0b741b8234c86065fb6954d32d427b3f7e14756f and fixed in 4.19.250 with commit 4f5877bdf7b593e988f1924f4c3df6523f80b39c Issue introduced in 4.15 with commit 0b741b8234c86065fb6954d32d427b3f7e14756f and fixed in 5.4.202 with commit 734a4d15142bb4c8ecad2d8ec70d7564e78ae34d Issue introduced in 4.15 with commit 0b741b8234c86065fb6954d32d427b3f7e14756f and fixed in 5.10.127 with commit 30bbfeb480ae8b5ee43199d72417b232590440c2 Issue introduced in 4.15 with commit 0b741b8234c86065fb6954d32d427b3f7e14756f and fixed in 5.15.51 with commit 10ba9d499a9fd82ed40897e734ba19870a879407 Issue introduced in 4.15 with commit 0b741b8234c86065fb6954d32d427b3f7e14756f and fixed in 5.18.8 with commit dcafd5463d8f20c4f90ddc138a5738adb99f74c8 Issue introduced in 4.15 with commit 0b741b8234c86065fb6954d32d427b3f7e14756f and fixed in 5.19 with commit 37d838de369b07b596c19ff3662bf0293fdb09ee 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-49678 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/soc/bcm/brcmstb/pm/pm-arm.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/4f5877bdf7b593e988f1924f4c3df6523f80b39c https://git.kernel.org/stable/c/734a4d15142bb4c8ecad2d8ec70d7564e78ae34d https://git.kernel.org/stable/c/30bbfeb480ae8b5ee43199d72417b232590440c2 https://git.kernel.org/stable/c/10ba9d499a9fd82ed40897e734ba19870a879407 https://git.kernel.org/stable/c/dcafd5463d8f20c4f90ddc138a5738adb99f74c8 https://git.kernel.org/stable/c/37d838de369b07b596c19ff3662bf0293fdb09ee
Powered by blists - more mailing lists