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: <2025030610-CVE-2024-58067-0807@gregkh> Date: Thu, 6 Mar 2025 16:54:20 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2024-58067: clk: mmp: pxa1908-mpmu: Fix a NULL vs IS_ERR() check Description =========== In the Linux kernel, the following vulnerability has been resolved: clk: mmp: pxa1908-mpmu: Fix a NULL vs IS_ERR() check The devm_kzalloc() function returns NULL on error, not error pointers. Update the check to match. The Linux kernel CVE team has assigned CVE-2024-58067 to this issue. Affected and fixed versions =========================== Issue introduced in 6.13 with commit ebac87cdd230685fc5245a61bde79c9100ac348a and fixed in 6.13.2 with commit 0869a7b2afdfcdd2beb0a5fb683119bcf39c0e9d Issue introduced in 6.13 with commit ebac87cdd230685fc5245a61bde79c9100ac348a and fixed in 6.14-rc1 with commit 7def56f841af22e07977e193eea002e085facbdb 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-2024-58067 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/clk/mmp/clk-pxa1908-mpmu.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/0869a7b2afdfcdd2beb0a5fb683119bcf39c0e9d https://git.kernel.org/stable/c/7def56f841af22e07977e193eea002e085facbdb
Powered by blists - more mailing lists