| 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: <2025030608-CVE-2024-58076-3dcc@gregkh> Date: Thu, 6 Mar 2025 17:14:09 +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-58076: clk: qcom: gcc-sm6350: Add missing parent_map for two clocks Description =========== In the Linux kernel, the following vulnerability has been resolved: clk: qcom: gcc-sm6350: Add missing parent_map for two clocks If a clk_rcg2 has a parent, it should also have parent_map defined, otherwise we'll get a NULL pointer dereference when calling clk_set_rate like the following: [ 3.388105] Call trace: [ 3.390664] qcom_find_src_index+0x3c/0x70 (P) [ 3.395301] qcom_find_src_index+0x1c/0x70 (L) [ 3.399934] _freq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] clk_core_determine_round_nolock+0x58/0xe4 [ 3.421414] clk_core_round_rate_nolock+0x48/0xfc [ 3.432974] clk_core_round_rate_nolock+0xd0/0xfc [ 3.444483] clk_core_set_rate_nolock+0x8c/0x300 [ 3.455886] clk_set_rate+0x38/0x14c Add the parent_map property for two clocks where it's missing and also un-inline the parent_data as well to keep the matching parent_map and parent_data together. The Linux kernel CVE team has assigned CVE-2024-58076 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 131abae905df99f63d825e47b4df100d34f518ce and fixed in 6.1.129 with commit 39336edd14a59dc086fb19957655e0f340bb28e8 Issue introduced in 5.15 with commit 131abae905df99f63d825e47b4df100d34f518ce and fixed in 6.6.78 with commit 08b77ed7cfaac62bba51ac7a0487409ec9fcbc84 Issue introduced in 5.15 with commit 131abae905df99f63d825e47b4df100d34f518ce and fixed in 6.12.14 with commit b6fe13566bf5676b1e3b72d2a06d875733e93ee6 Issue introduced in 5.15 with commit 131abae905df99f63d825e47b4df100d34f518ce and fixed in 6.13.3 with commit 3e567032233a240b903dc11c9f18eeb3faa10ffa Issue introduced in 5.15 with commit 131abae905df99f63d825e47b4df100d34f518ce and fixed in 6.14-rc1 with commit 96fe1a7ee477d701cfc98ab9d3c730c35d966861 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-58076 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/qcom/gcc-sm6350.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/39336edd14a59dc086fb19957655e0f340bb28e8 https://git.kernel.org/stable/c/08b77ed7cfaac62bba51ac7a0487409ec9fcbc84 https://git.kernel.org/stable/c/b6fe13566bf5676b1e3b72d2a06d875733e93ee6 https://git.kernel.org/stable/c/3e567032233a240b903dc11c9f18eeb3faa10ffa https://git.kernel.org/stable/c/96fe1a7ee477d701cfc98ab9d3c730c35d966861
Powered by blists - more mailing lists