First published: Thu Mar 06 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: clk: qcom: dispcc-sm6350: Add missing parent_map for a clock 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 the clock where it's missing and also un-inline the parent_data as well to keep the matching parent_map and parent_data together.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Linux Kernel | >=5.18<6.1.129 | |
Linux Kernel | >=6.2<6.6.78 | |
Linux Kernel | >=6.7<6.12.14 | |
Linux Kernel | >=6.13<6.13.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-58080 is classified as a low severity vulnerability due to the potential for NULL pointer dereference.
To fix CVE-2024-58080, ensure that the parent_map is defined for clk_rcg2 instances in the Linux kernel.
CVE-2024-58080 affects the Linux kernel, specifically within the qcom dispcc-sm6350 clock driver.
The impact of CVE-2024-58080 includes a potential crash of the system due to a NULL pointer dereference when invoking clk_set_rate.
CVE-2024-58080 was resolved in a recent update of the Linux kernel, emphasizing the need for timely system updates.