Skip to main content

CVE-2024-50240: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2024-50240cvecve-2024-50240
Published: Sat Nov 09 2024 (11/09/2024, 10:14:50 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usb: fix NULL-deref on runtime suspend Commit 413db06c05e7 ("phy: qcom-qmp-usb: clean up probe initialisation") removed most users of the platform device driver data, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend. Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with this driver.

AI-Powered Analysis

AILast updated: 06/28/2025, 13:25:00 UTC

Technical Analysis

CVE-2024-50240 is a vulnerability identified in the Linux kernel specifically affecting the Qualcomm QMP USB PHY driver (phy: qcom-qmp-usb). The issue stems from a regression introduced by commit 413db06c05e7, which cleaned up the probe initialization of the platform device driver data but inadvertently removed the initialization of driver data still required by runtime power management (PM) callbacks. This omission leads to a NULL pointer dereference when the runtime suspend operation is invoked, causing a potential kernel crash or denial of service. Runtime PM is not enabled by default for this driver and must be manually activated via sysfs, which limits the exposure surface. The vulnerability is a classic use-after-free or NULL pointer dereference bug triggered during power management operations, specifically runtime suspend. No known exploits are currently reported in the wild, and the vulnerability was reserved and published in late 2024. The affected Linux kernel versions are identified by the commit hash 413db06c05e7, indicating the regression was introduced and fixed around this patch. The vulnerability impacts the stability and availability of systems using this specific Qualcomm USB PHY driver with runtime PM enabled, potentially causing kernel panics or system crashes during suspend operations. Since the vulnerability requires manual enabling of runtime PM and affects a niche driver, the attack surface is limited but still relevant for embedded or mobile devices using Qualcomm hardware with Linux kernels containing this regression.

Potential Impact

For European organizations, the impact of CVE-2024-50240 is primarily related to system availability and stability in environments using Linux-based devices with Qualcomm QMP USB PHY hardware where runtime power management is enabled. This includes embedded systems, IoT devices, and specialized industrial or telecommunications equipment that rely on Linux kernels with this driver. A successful exploitation would cause kernel crashes or denial of service, potentially disrupting critical operations or services. While the vulnerability does not directly expose confidentiality or integrity risks, the resulting system instability could lead to operational downtime, impacting business continuity. The limited default exposure due to runtime PM being disabled by default reduces the likelihood of widespread impact but organizations with custom Linux builds enabling runtime PM for power efficiency or device management should prioritize patching. European sectors such as telecommunications, manufacturing, and automotive industries that deploy embedded Linux systems with Qualcomm chipsets could be affected. Additionally, organizations involved in Linux kernel development or distribution in Europe must ensure the fix is incorporated to prevent regressions in their releases.

Mitigation Recommendations

To mitigate CVE-2024-50240, European organizations should: 1) Apply the official Linux kernel patch that restores the driver data initialization in the Qualcomm QMP USB PHY driver probe function, ensuring the runtime PM callbacks have valid data references. 2) Audit and verify if runtime power management is enabled on affected devices, especially in embedded or specialized Linux deployments, and consider disabling runtime PM temporarily if patching is not immediately feasible. 3) Conduct thorough testing of power management features post-patching to confirm stability and absence of regressions. 4) Monitor Linux kernel updates and vendor advisories for backported fixes in distributions commonly used in Europe, such as Debian, Ubuntu, Red Hat, SUSE, and others. 5) For organizations building custom kernels, integrate the patch into their build pipelines and validate the fix in their hardware environments. 6) Implement robust monitoring to detect kernel panics or unexpected reboots that could indicate exploitation attempts or instability related to this vulnerability. 7) Educate system administrators and embedded device maintainers about the specific conditions under which this vulnerability can be triggered to reduce inadvertent enabling of runtime PM without patching.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-10-21T19:36:19.976Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9824c4522896dcbdf5ff

Added to database: 5/21/2025, 9:08:52 AM

Last enriched: 6/28/2025, 1:25:00 PM

Last updated: 7/22/2025, 5:58:04 AM

Views: 6

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats