| 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: <2025022601-CVE-2022-49462-52fb@gregkh> Date: Wed, 26 Feb 2025 03:12:16 +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-49462: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. a6xx_gmu_init() passes the node to of_find_device_by_node() and of_dma_configure(), of_find_device_by_node() will takes its reference, of_dma_configure() doesn't need the node after usage. Add missing of_node_put() to avoid refcount leak. The Linux kernel CVE team has assigned CVE-2022-49462 to this issue. Affected and fixed versions =========================== Issue introduced in 4.19 with commit 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and fixed in 5.4.198 with commit 6832e36f156ea35a6ed74bca72727806116effdd Issue introduced in 4.19 with commit 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and fixed in 5.10.121 with commit 48e82ce8cdb19c20a5020fa446b286d6a147450c Issue introduced in 4.19 with commit 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and fixed in 5.15.46 with commit edff4c1af831d0c02e654eed9da7d74174de49d5 Issue introduced in 4.19 with commit 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and fixed in 5.17.14 with commit 65ddbc0d26824e2a5d6154d01d8cf39344900213 Issue introduced in 4.19 with commit 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and fixed in 5.18.3 with commit 06907a374f1b74f8f2fb30720dc6df81331e4fb5 Issue introduced in 4.19 with commit 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and fixed in 5.19 with commit c56de483093d7ad0782327f95dda7da97bc4c315 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-49462 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/gpu/drm/msm/adreno/a6xx_gpu.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/6832e36f156ea35a6ed74bca72727806116effdd https://git.kernel.org/stable/c/48e82ce8cdb19c20a5020fa446b286d6a147450c https://git.kernel.org/stable/c/edff4c1af831d0c02e654eed9da7d74174de49d5 https://git.kernel.org/stable/c/65ddbc0d26824e2a5d6154d01d8cf39344900213 https://git.kernel.org/stable/c/06907a374f1b74f8f2fb30720dc6df81331e4fb5 https://git.kernel.org/stable/c/c56de483093d7ad0782327f95dda7da97bc4c315
Powered by blists - more mailing lists