CVE-2024-58076

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

State
Published
Severity
5.5 Medium
Published
Mar 6, 2025
Updated
May 11, 2026
Reserved
Mar 6, 2025

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.15.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HCISA-ADP

Weaknesses

Affected Products

ProductVersions
LinuxLinux
  • 131abae905df99f63d825e47b4df100d34f518ce to before 175af15551ed5aa6af16ff97aff75cfffb42da21Affected
  • 131abae905df99f63d825e47b4df100d34f518ce to before 39336edd14a59dc086fb19957655e0f340bb28e8Affected
  • 131abae905df99f63d825e47b4df100d34f518ce to before 08b77ed7cfaac62bba51ac7a0487409ec9fcbc84Affected
  • 131abae905df99f63d825e47b4df100d34f518ce to before b6fe13566bf5676b1e3b72d2a06d875733e93ee6Affected
  • 131abae905df99f63d825e47b4df100d34f518ce to before 3e567032233a240b903dc11c9f18eeb3faa10ffaAffected
  • 131abae905df99f63d825e47b4df100d34f518ce to before 96fe1a7ee477d701cfc98ab9d3c730c35d966861Affected
LinuxLinux
  • 5.15Affected
  • before 5.15Not affected
  • 5.15.179 through 5.15.*Not affected
  • 6.1.129 through 6.1.*Not affected
  • 6.6.78 through 6.6.*Not affected
  • 6.12.14 through 6.12.*Not affected
  • 6.13.3 through 6.13.*Not affected
  • 6.14 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.