CVE-2024-58080 clk: qcom: dispcc-sm6350: Add missing parent_map for a clock
A missing parent map in the Qualcomm display clock driver causes a null pointer dereference, leading to a kernel crash when setting the clock rate.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-58080?
CVE-2024-58080 is a medium-severity vulnerability in Linux kernel, published on 6 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-476
Which versions are affected by CVE-2024-58080?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2024-58080?
Apply the vendor's patch.
Is CVE-2024-58080 being exploited?
There is no known exploitation of CVE-2024-58080 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as BELL-CVE-2024-58080, DEBIAN-CVE-2024-58080, GHSA-vrf6-366f-p2hr, ROOT-OS-UBUNTU-2404-CVE-2024-58080, UBUNTU-CVE-2024-58080.