CVE-2024-58076

clk: qcom: gcc-sm6350: Add missing parent_map for two clocks

MEDIUM

5.5

CVSS Score

Published: March 6, 2025 at 04:13 PM UTC

Updated: June 17, 2026 at 08:14 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.15 ≤ v < 5.15.1795.15 ≤ v < 6.1.1295.15 ≤ v < 6.12.145.15 ≤ v < 6.13.35.15 ≤ v < 6.145.15 ≤ v < 6.6.785.16 ≤ v < 6.1.1296.13 ≤ v < 6.13.36.2 ≤ v < 6.6.786.7 ≤ v < 6.12.14131abae905df99f63d825e47b4df100d34f518ce5.15

Vendor states this is fixed in 08b77ed7cfaac62bba51ac7a0487409ec9fcbc84 (fixed)

Vendor states this is fixed in 175af15551ed5aa6af16ff97aff75cfffb42da21 (fixed)

Vendor states this is fixed in 39336edd14a59dc086fb19957655e0f340bb28e8 (fixed)

Vendor states this is fixed in 3e567032233a240b903dc11c9f18eeb3faa10ffa (fixed)

Vendor states this is fixed in 96fe1a7ee477d701cfc98ab9d3c730c35d966861 (fixed)

Vendor states this is fixed in b6fe13566bf5676b1e3b72d2a06d875733e93ee6 (fixed)

Vendor states this is fixed in 5.15 (unaffected)

Vendor states this is fixed in 5.15.179 (unaffected)

Vendor states this is fixed in 6.1.129 (unaffected)

Vendor states this is fixed in 6.12.14 (unaffected)

Vendor states this is fixed in 6.13.3 (unaffected)

Vendor states this is fixed in 6.14 (unaffected)

Vendor states this is fixed in 6.6.78 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references