CVE-2024-58068: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized If a driver calls dev_pm_opp_find_bw_ceil/floor() the retrieve bandwidth from the OPP table but the bandwidth table was not created because the interconnect properties were missing in the OPP consumer node, the kernel will crash with: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004 ... pc : _read_bw+0x8/0x10 lr : _opp_table_find_key+0x9c/0x174 ... Call trace: _read_bw+0x8/0x10 (P) _opp_table_find_key+0x9c/0x174 (L) _find_key+0x98/0x168 dev_pm_opp_find_bw_ceil+0x50/0x88 ... In order to fix the crash, create an assert function to check if the bandwidth table was created before trying to get a bandwidth with _read_bw().
AI Analysis
Technical Summary
CVE-2024-58068 is a vulnerability identified in the Linux kernel related to the Operating Performance Points (OPP) framework, specifically in the handling of bandwidth tables used by device power management. The issue arises when a driver calls the functions dev_pm_opp_find_bw_ceil() or dev_pm_opp_find_bw_floor() to retrieve bandwidth information from the OPP table, but the bandwidth table has not been initialized. This lack of initialization occurs if the interconnect properties are missing in the OPP consumer node. Under these conditions, the kernel attempts to dereference a NULL pointer, leading to a kernel crash with an error message indicating an inability to handle a NULL pointer dereference at a specific virtual address. The crash occurs in the _read_bw() function, which is called during bandwidth retrieval, propagating through _opp_table_find_key() and dev_pm_opp_find_bw_ceil(). The root cause is the absence of a check to verify that the bandwidth table exists before attempting to read from it. The fix implemented involves adding an assertion to ensure the bandwidth table is created before any bandwidth retrieval attempts, preventing the NULL pointer dereference and subsequent kernel panic. This vulnerability affects Linux kernel versions identified by the commit hash add1dc094a7456d3c56782b7478940b6a550c7ed and potentially others with similar code paths. No known exploits are reported in the wild at this time, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions, especially those utilizing device drivers that interact with the OPP framework for power management and bandwidth control. The impact manifests as a denial of service (DoS) condition due to kernel crashes, which can disrupt critical services, reduce system availability, and potentially cause data loss or corruption if crashes occur during sensitive operations. Systems in embedded environments, telecommunications, industrial control, and cloud infrastructure that rely on Linux kernels with these drivers are particularly vulnerable. While the vulnerability does not directly lead to privilege escalation or data breach, the resulting instability can degrade operational continuity and increase maintenance overhead. Organizations with large Linux deployments, including servers, network devices, and IoT devices, may experience increased downtime or require emergency patching. Given that no authentication or user interaction is required to trigger the crash (it depends on driver behavior), the vulnerability could be exploited by local processes or malicious drivers, increasing the attack surface in multi-tenant or shared environments.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernels to versions where the patch for CVE-2024-58068 has been applied. Kernel maintainers have introduced assertions to verify bandwidth table initialization before access, preventing the NULL pointer dereference. Organizations should: 1) Identify all systems running affected kernel versions, especially those with custom or third-party drivers that may interact with the OPP framework. 2) Test and deploy kernel updates from trusted sources that include the fix. 3) Review device tree configurations and ensure interconnect properties are correctly defined in OPP consumer nodes to prevent uninitialized bandwidth tables. 4) Implement monitoring for kernel panics and crashes related to power management subsystems to detect exploitation attempts early. 5) For embedded and IoT devices where kernel updates are challenging, consider isolating vulnerable devices or restricting access to trusted users and processes to reduce risk. 6) Engage with hardware and software vendors to confirm patch availability and deployment timelines. These steps go beyond generic advice by focusing on configuration validation, targeted patching, and proactive monitoring specific to the OPP and power management components.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-58068: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized If a driver calls dev_pm_opp_find_bw_ceil/floor() the retrieve bandwidth from the OPP table but the bandwidth table was not created because the interconnect properties were missing in the OPP consumer node, the kernel will crash with: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004 ... pc : _read_bw+0x8/0x10 lr : _opp_table_find_key+0x9c/0x174 ... Call trace: _read_bw+0x8/0x10 (P) _opp_table_find_key+0x9c/0x174 (L) _find_key+0x98/0x168 dev_pm_opp_find_bw_ceil+0x50/0x88 ... In order to fix the crash, create an assert function to check if the bandwidth table was created before trying to get a bandwidth with _read_bw().
AI-Powered Analysis
Technical Analysis
CVE-2024-58068 is a vulnerability identified in the Linux kernel related to the Operating Performance Points (OPP) framework, specifically in the handling of bandwidth tables used by device power management. The issue arises when a driver calls the functions dev_pm_opp_find_bw_ceil() or dev_pm_opp_find_bw_floor() to retrieve bandwidth information from the OPP table, but the bandwidth table has not been initialized. This lack of initialization occurs if the interconnect properties are missing in the OPP consumer node. Under these conditions, the kernel attempts to dereference a NULL pointer, leading to a kernel crash with an error message indicating an inability to handle a NULL pointer dereference at a specific virtual address. The crash occurs in the _read_bw() function, which is called during bandwidth retrieval, propagating through _opp_table_find_key() and dev_pm_opp_find_bw_ceil(). The root cause is the absence of a check to verify that the bandwidth table exists before attempting to read from it. The fix implemented involves adding an assertion to ensure the bandwidth table is created before any bandwidth retrieval attempts, preventing the NULL pointer dereference and subsequent kernel panic. This vulnerability affects Linux kernel versions identified by the commit hash add1dc094a7456d3c56782b7478940b6a550c7ed and potentially others with similar code paths. No known exploits are reported in the wild at this time, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions, especially those utilizing device drivers that interact with the OPP framework for power management and bandwidth control. The impact manifests as a denial of service (DoS) condition due to kernel crashes, which can disrupt critical services, reduce system availability, and potentially cause data loss or corruption if crashes occur during sensitive operations. Systems in embedded environments, telecommunications, industrial control, and cloud infrastructure that rely on Linux kernels with these drivers are particularly vulnerable. While the vulnerability does not directly lead to privilege escalation or data breach, the resulting instability can degrade operational continuity and increase maintenance overhead. Organizations with large Linux deployments, including servers, network devices, and IoT devices, may experience increased downtime or require emergency patching. Given that no authentication or user interaction is required to trigger the crash (it depends on driver behavior), the vulnerability could be exploited by local processes or malicious drivers, increasing the attack surface in multi-tenant or shared environments.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernels to versions where the patch for CVE-2024-58068 has been applied. Kernel maintainers have introduced assertions to verify bandwidth table initialization before access, preventing the NULL pointer dereference. Organizations should: 1) Identify all systems running affected kernel versions, especially those with custom or third-party drivers that may interact with the OPP framework. 2) Test and deploy kernel updates from trusted sources that include the fix. 3) Review device tree configurations and ensure interconnect properties are correctly defined in OPP consumer nodes to prevent uninitialized bandwidth tables. 4) Implement monitoring for kernel panics and crashes related to power management subsystems to detect exploitation attempts early. 5) For embedded and IoT devices where kernel updates are challenging, consider isolating vulnerable devices or restricting access to trusted users and processes to reduce risk. 6) Engage with hardware and software vendors to confirm patch availability and deployment timelines. These steps go beyond generic advice by focusing on configuration validation, targeted patching, and proactive monitoring specific to the OPP and power management components.
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.181Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9822c4522896dcbde2b0
Added to database: 5/21/2025, 9:08:50 AM
Last enriched: 6/28/2025, 5:55:00 AM
Last updated: 8/4/2025, 12:35:26 AM
Views: 11
Related Threats
CVE-2025-43490: CWE-59 Improper Link Resolution Before File Access ('Link Following') in HP, Inc. HP Hotkey Support Software
MediumCVE-2025-9060: CWE-20 Improper Input Validation in MSoft MFlash
CriticalCVE-2025-8675: CWE-918 Server-Side Request Forgery (SSRF) in Drupal AI SEO Link Advisor
MediumCVE-2025-8362: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Drupal GoogleTag Manager
MediumCVE-2025-8361: CWE-962 Missing Authorization in Drupal Config Pages
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.