| 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: <2025120844-CVE-2023-53757-8c1e@gregkh> Date: Mon, 8 Dec 2025 10:19:56 +0900 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53757: irqchip/irq-mvebu-gicp: Fix refcount leak in mvebu_gicp_probe From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: irqchip/irq-mvebu-gicp: Fix refcount leak in mvebu_gicp_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak. The Linux kernel CVE team has assigned CVE-2023-53757 to this issue. Affected and fixed versions =========================== Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 4.14.308 with commit d6b99b9b5e354f9c801a3cc3b1d4881d920e1718 Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 4.19.276 with commit 4545d7a70ce0fc78b1d3c33c4a0939a86f363b57 Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 5.4.235 with commit c7d78d36e19eeb74a1c12799fbadbcdbaf36c0bd Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 5.10.173 with commit cee12e8be8e227731a845ae43a4c9ce2e404be45 Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 5.15.99 with commit 88cb93d3a16f706bd7213f8a5882c394e5d10c4e Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 6.1.16 with commit bb755e020abc24793b9411c9419ed43f07f9a03d Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 6.2.3 with commit 91e149b201bdb68c77011d50d011e47fadbcc8bd Issue introduced in 4.13 with commit a68a63cb4dfc30e8a79b444aabc7747bb7621acf and fixed in 6.3 with commit 9419e700021a393f67be36abd0c4f3acc6139041 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-2023-53757 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/irqchip/irq-mvebu-gicp.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/d6b99b9b5e354f9c801a3cc3b1d4881d920e1718 https://git.kernel.org/stable/c/4545d7a70ce0fc78b1d3c33c4a0939a86f363b57 https://git.kernel.org/stable/c/c7d78d36e19eeb74a1c12799fbadbcdbaf36c0bd https://git.kernel.org/stable/c/cee12e8be8e227731a845ae43a4c9ce2e404be45 https://git.kernel.org/stable/c/88cb93d3a16f706bd7213f8a5882c394e5d10c4e https://git.kernel.org/stable/c/bb755e020abc24793b9411c9419ed43f07f9a03d https://git.kernel.org/stable/c/91e149b201bdb68c77011d50d011e47fadbcc8bd https://git.kernel.org/stable/c/9419e700021a393f67be36abd0c4f3acc6139041
Powered by blists - more mailing lists