CVE-2024-58076: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2024-58076 is a vulnerability identified in the Linux kernel specifically related to the Qualcomm clock controller driver (gcc-sm6350). The issue arises because certain clk_rcg2 clocks that have a parent clock lack a corresponding parent_map definition. In the Linux kernel's clock framework, clk_rcg2 structures require a parent_map to correctly map parent clocks. Without this mapping, when the kernel attempts to set the clock rate via clk_set_rate, it can dereference a NULL pointer, leading to a kernel crash (NULL pointer dereference). The stack trace provided in the vulnerability description shows the failure occurring during the frequency determination and rate setting functions within the clock core subsystem. The root cause is a missing parent_map property for two specific clocks in the Qualcomm gcc-sm6350 clock driver. The fix involves adding the missing parent_map entries and adjusting the parent_data to be non-inlined to maintain consistency between parent_map and parent_data. This vulnerability is a stability and availability issue affecting Linux kernel versions containing the affected Qualcomm clock driver code. It does not appear to be exploitable for privilege escalation or code execution but can cause a denial of service (DoS) by crashing the kernel when the affected clocks are manipulated. The vulnerability is not known to be exploited in the wild and no CVSS score has been assigned yet. The affected versions are identified by a specific git commit hash, indicating this is a recent and targeted fix in the Linux kernel source code.
Potential Impact
For European organizations, the primary impact of CVE-2024-58076 is a potential denial of service condition on Linux systems running kernels with the affected Qualcomm clock driver (gcc-sm6350). This is particularly relevant for devices using Qualcomm Snapdragon 6350 SoCs or similar hardware platforms that incorporate this clock controller. Such devices may include embedded systems, IoT devices, mobile devices, or specialized industrial equipment running Linux. A kernel crash caused by this vulnerability could lead to system downtime, impacting availability of critical services or devices. While this vulnerability does not directly compromise confidentiality or integrity, the resulting instability could disrupt operations, especially in environments relying on continuous uptime such as telecommunications infrastructure, industrial control systems, or network equipment. European organizations deploying Linux-based devices with Qualcomm hardware should be aware of this risk, particularly those in sectors like manufacturing, telecommunications, and critical infrastructure. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to accidental or malicious triggering of the kernel crash. The impact is less severe on general-purpose Linux servers or desktops that do not use the affected Qualcomm clock driver.
Mitigation Recommendations
To mitigate CVE-2024-58076, organizations should: 1) Identify Linux systems running kernels with Qualcomm gcc-sm6350 clock drivers or related Qualcomm SoCs that might be affected. 2) Apply the official Linux kernel patches that add the missing parent_map entries and fix the parent_data handling as soon as they are available from trusted sources or Linux distribution vendors. 3) For embedded or IoT devices, coordinate with hardware vendors or device manufacturers to obtain updated firmware or kernel versions incorporating the fix. 4) Implement monitoring to detect kernel crashes or reboots that could indicate triggering of this vulnerability. 5) Restrict access to interfaces or software components that might invoke clk_set_rate on the affected clocks, reducing the chance of accidental or malicious exploitation. 6) Test updated kernels in staging environments to ensure stability before deployment. 7) Maintain an inventory of devices with Qualcomm hardware to prioritize patching efforts. These steps go beyond generic advice by focusing on hardware-specific identification, vendor coordination, and operational monitoring tailored to this vulnerability.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Finland
CVE-2024-58076: Vulnerability in Linux Linux
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.
AI-Powered Analysis
Technical Analysis
CVE-2024-58076 is a vulnerability identified in the Linux kernel specifically related to the Qualcomm clock controller driver (gcc-sm6350). The issue arises because certain clk_rcg2 clocks that have a parent clock lack a corresponding parent_map definition. In the Linux kernel's clock framework, clk_rcg2 structures require a parent_map to correctly map parent clocks. Without this mapping, when the kernel attempts to set the clock rate via clk_set_rate, it can dereference a NULL pointer, leading to a kernel crash (NULL pointer dereference). The stack trace provided in the vulnerability description shows the failure occurring during the frequency determination and rate setting functions within the clock core subsystem. The root cause is a missing parent_map property for two specific clocks in the Qualcomm gcc-sm6350 clock driver. The fix involves adding the missing parent_map entries and adjusting the parent_data to be non-inlined to maintain consistency between parent_map and parent_data. This vulnerability is a stability and availability issue affecting Linux kernel versions containing the affected Qualcomm clock driver code. It does not appear to be exploitable for privilege escalation or code execution but can cause a denial of service (DoS) by crashing the kernel when the affected clocks are manipulated. The vulnerability is not known to be exploited in the wild and no CVSS score has been assigned yet. The affected versions are identified by a specific git commit hash, indicating this is a recent and targeted fix in the Linux kernel source code.
Potential Impact
For European organizations, the primary impact of CVE-2024-58076 is a potential denial of service condition on Linux systems running kernels with the affected Qualcomm clock driver (gcc-sm6350). This is particularly relevant for devices using Qualcomm Snapdragon 6350 SoCs or similar hardware platforms that incorporate this clock controller. Such devices may include embedded systems, IoT devices, mobile devices, or specialized industrial equipment running Linux. A kernel crash caused by this vulnerability could lead to system downtime, impacting availability of critical services or devices. While this vulnerability does not directly compromise confidentiality or integrity, the resulting instability could disrupt operations, especially in environments relying on continuous uptime such as telecommunications infrastructure, industrial control systems, or network equipment. European organizations deploying Linux-based devices with Qualcomm hardware should be aware of this risk, particularly those in sectors like manufacturing, telecommunications, and critical infrastructure. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to accidental or malicious triggering of the kernel crash. The impact is less severe on general-purpose Linux servers or desktops that do not use the affected Qualcomm clock driver.
Mitigation Recommendations
To mitigate CVE-2024-58076, organizations should: 1) Identify Linux systems running kernels with Qualcomm gcc-sm6350 clock drivers or related Qualcomm SoCs that might be affected. 2) Apply the official Linux kernel patches that add the missing parent_map entries and fix the parent_data handling as soon as they are available from trusted sources or Linux distribution vendors. 3) For embedded or IoT devices, coordinate with hardware vendors or device manufacturers to obtain updated firmware or kernel versions incorporating the fix. 4) Implement monitoring to detect kernel crashes or reboots that could indicate triggering of this vulnerability. 5) Restrict access to interfaces or software components that might invoke clk_set_rate on the affected clocks, reducing the chance of accidental or malicious exploitation. 6) Test updated kernels in staging environments to ensure stability before deployment. 7) Maintain an inventory of devices with Qualcomm hardware to prioritize patching efforts. These steps go beyond generic advice by focusing on hardware-specific identification, vendor coordination, and operational monitoring tailored to this vulnerability.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-03-06T15:52:09.182Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9822c4522896dcbde2f8
Added to database: 5/21/2025, 9:08:50 AM
Last enriched: 6/28/2025, 5:56:18 AM
Last updated: 7/26/2025, 5:25:40 PM
Views: 10
Related Threats
CVE-2025-8874: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in litonice13 Master Addons – Elementor Addons with White Label, Free Widgets, Hover Effects, Conditions, & Animations
MediumCVE-2025-8767: CWE-1236 Improper Neutralization of Formula Elements in a CSV File in anwppro AnWP Football Leagues
MediumCVE-2025-8482: CWE-862 Missing Authorization in 10up Simple Local Avatars
MediumCVE-2025-8418: CWE-862 Missing Authorization in bplugins B Slider- Gutenberg Slider Block for WP
HighCVE-2025-47444: CWE-201 Insertion of Sensitive Information Into Sent Data in Liquid Web GiveWP
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.