CVE-2024-58080

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: qcom: dispcc-sm6350: Add missing parent_map for a clock<br /> <br /> If a clk_rcg2 has a parent, it should also have parent_map defined,<br /> otherwise we&amp;#39;ll get a NULL pointer dereference when calling clk_set_rate<br /> like the following:<br /> <br /> [ 3.388105] Call trace:<br /> [ 3.390664] qcom_find_src_index+0x3c/0x70 (P)<br /> [ 3.395301] qcom_find_src_index+0x1c/0x70 (L)<br /> [ 3.399934] _freq_tbl_determine_rate+0x48/0x100<br /> [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28<br /> [ 3.409387] clk_core_determine_round_nolock+0x58/0xe4<br /> [ 3.421414] clk_core_round_rate_nolock+0x48/0xfc<br /> [ 3.432974] clk_core_round_rate_nolock+0xd0/0xfc<br /> [ 3.444483] clk_core_set_rate_nolock+0x8c/0x300<br /> [ 3.455886] clk_set_rate+0x38/0x14c<br /> <br /> Add the parent_map property for the clock where it&amp;#39;s missing and also<br /> un-inline the parent_data as well to keep the matching parent_map and<br /> parent_data together.