Kernel crash via missing clock parent maps
Published Mar 6, 2025 · Updated May 11, 2026
NULL pointer dereference in the Qualcomm SM6350 clock driver in Linux allows local users to crash the system through a clock rate change. Two clk_rcg2 definitions in drivers/clk/qcom/gcc-sm6350.c declare parents without matching parent_map tables, so qcom_find_src_index dereferences a null map during clk_set_rate. Reachability requires local low-privilege access on a system using the affected SM6350 clock controller; the reported consequence is a kernel crash without confidentiality or integrity impact.
Summary
What happened
NULL pointer dereference in the Qualcomm SM6350 clock driver in Linux allows local users to crash the system through a clock rate change. Two clk_rcg2 definitions in drivers/clk/qcom/gcc-sm6350.c declare parents without matching parent_map tables, so qcom_find_src_index dereferences a null map during clk_set_rate. Reachability requires local low-privilege access on a system using the affected SM6350 clock controller; the reported consequence is a kernel crash without confidentiality or integrity impact.
The record
- CVE
- CVE-2024-58076
- Published
- Mar 6, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=131abae905df99f63d825e47b4df100d34f518ce <08b77ed7cfaac62bba51ac7a0487409ec9fcbc84
- Affected versionversion=131abae905df99f63d825e47b4df100d34f518ce <175af15551ed5aa6af16ff97aff75cfffb42da21
- Affected versionversion=131abae905df99f63d825e47b4df100d34f518ce <39336edd14a59dc086fb19957655e0f340bb28e8
- Affected versionversion=131abae905df99f63d825e47b4df100d34f518ce <3e567032233a240b903dc11c9f18eeb3faa10ffa
- Affected versionversion=131abae905df99f63d825e47b4df100d34f518ce <96fe1a7ee477d701cfc98ab9d3c730c35d966861
- Affected versionversion=131abae905df99f63d825e47b4df100d34f518ce <b6fe13566bf5676b1e3b72d2a06d875733e93ee6
- Affected versionversion=5.15
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo