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: <2024111933-CVE-2024-53069-2786@gregkh> Date: Tue, 19 Nov 2024 18:22:40 +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-53069: firmware: qcom: scm: fix a NULL-pointer dereference Description =========== In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: fix a NULL-pointer dereference Some SCM calls can be invoked with __scm being NULL (the driver may not have been and will not be probed as there's no SCM entry in device-tree). Make sure we don't dereference a NULL pointer. The Linux kernel CVE team has assigned CVE-2024-53069 to this issue. Affected and fixed versions =========================== Issue introduced in 6.11 with commit 449d0d84bcd8 and fixed in 6.11.8 with commit 3d36e2b1d803 Issue introduced in 6.11 with commit 449d0d84bcd8 and fixed in 6.12 with commit ca61d6836e6f 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-53069 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/firmware/qcom/qcom_scm.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/3d36e2b1d803f0d1cc674115d295a8f20ddb9268 https://git.kernel.org/stable/c/ca61d6836e6f4442a77762e1074d2706a2a6e578
Powered by blists - more mailing lists