CVE-2024-45015: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() For cases where the crtc's connectors_changed was set without enable/active getting toggled , there is an atomic_enable() call followed by an atomic_disable() but without an atomic_mode_set(). This results in a NULL ptr access for the dpu_encoder_get_drm_fmt() call in the atomic_enable() as the dpu_encoder's connector was cleared in the atomic_disable() but not re-assigned as there was no atomic_mode_set() call. Fix the NULL ptr access by moving the assignment for atomic_enable() and also use drm_atomic_get_new_connector_for_encoder() to get the connector from the atomic_state. Patchwork: https://patchwork.freedesktop.org/patch/606729/
AI Analysis
Technical Summary
CVE-2024-45015 is a vulnerability identified in the Linux kernel, specifically within the Direct Rendering Manager (DRM) subsystem for the MSM (Qualcomm Snapdragon) Display Processing Unit (DPU) driver. The issue arises from improper handling of connector assignments during atomic state transitions in the DRM atomic modesetting framework. In detail, when the crtc's connectors_changed flag is set without toggling enable or active states, the code sequence calls atomic_enable() followed by atomic_disable() but omits an atomic_mode_set() call. This leads to a situation where the dpu_encoder's connector pointer is cleared during atomic_disable() but not reassigned before the subsequent atomic_enable() call. As a result, the function dpu_encoder_get_drm_fmt() dereferences a NULL pointer, causing a kernel NULL pointer dereference and likely a kernel panic or system crash. The fix involves moving the connector assignment into atomic_enable() and using drm_atomic_get_new_connector_for_encoder() to correctly retrieve the connector from the atomic state, preventing the NULL pointer dereference. This vulnerability affects Linux kernel versions containing the affected commit hashes referenced, primarily impacting devices using the MSM DPU driver for display rendering. No known exploits are reported in the wild as of the publication date (September 11, 2024).
Potential Impact
For European organizations, the impact of CVE-2024-45015 depends on the deployment of Linux systems running kernels with the vulnerable MSM DPU driver, which is predominantly found in devices using Qualcomm Snapdragon SoCs, such as smartphones, embedded systems, and some IoT devices. Enterprises relying on Linux-based embedded devices for critical operations, including telecommunications infrastructure, industrial control systems, or mobile device fleets, could experience system crashes or denial of service due to kernel panics triggered by this vulnerability. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting denial of service can disrupt business continuity, especially in environments where uptime is critical. Additionally, devices that rely on graphical output or display rendering may become unresponsive, impacting user operations or monitoring capabilities. Given the absence of known exploits, the immediate threat level is moderate; however, the potential for future exploitation exists if attackers develop triggers for the NULL pointer dereference. European organizations with embedded Linux devices or mobile device management responsibilities should be vigilant, as disruption in these systems could affect sectors like manufacturing, telecommunications, and public services.
Mitigation Recommendations
To mitigate CVE-2024-45015, organizations should: 1) Identify and inventory all Linux-based devices using Qualcomm MSM DPU drivers, particularly those running kernels with the affected commit hashes. 2) Apply the official Linux kernel patches that move the connector assignment to atomic_enable() and correctly retrieve the connector from the atomic state, as referenced in the patchwork link (https://patchwork.freedesktop.org/patch/606729/). 3) For devices where kernel patching is not immediately feasible, consider implementing kernel-level monitoring to detect and alert on kernel NULL pointer dereferences or crashes related to the DRM subsystem. 4) Engage with device vendors and OEMs to obtain updated firmware or kernel versions incorporating the fix. 5) Implement robust device management policies to ensure timely updates and minimize exposure. 6) Test patches in controlled environments before deployment to avoid unintended disruptions. 7) Monitor security advisories for any emerging exploit developments related to this vulnerability.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-45015: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() For cases where the crtc's connectors_changed was set without enable/active getting toggled , there is an atomic_enable() call followed by an atomic_disable() but without an atomic_mode_set(). This results in a NULL ptr access for the dpu_encoder_get_drm_fmt() call in the atomic_enable() as the dpu_encoder's connector was cleared in the atomic_disable() but not re-assigned as there was no atomic_mode_set() call. Fix the NULL ptr access by moving the assignment for atomic_enable() and also use drm_atomic_get_new_connector_for_encoder() to get the connector from the atomic_state. Patchwork: https://patchwork.freedesktop.org/patch/606729/
AI-Powered Analysis
Technical Analysis
CVE-2024-45015 is a vulnerability identified in the Linux kernel, specifically within the Direct Rendering Manager (DRM) subsystem for the MSM (Qualcomm Snapdragon) Display Processing Unit (DPU) driver. The issue arises from improper handling of connector assignments during atomic state transitions in the DRM atomic modesetting framework. In detail, when the crtc's connectors_changed flag is set without toggling enable or active states, the code sequence calls atomic_enable() followed by atomic_disable() but omits an atomic_mode_set() call. This leads to a situation where the dpu_encoder's connector pointer is cleared during atomic_disable() but not reassigned before the subsequent atomic_enable() call. As a result, the function dpu_encoder_get_drm_fmt() dereferences a NULL pointer, causing a kernel NULL pointer dereference and likely a kernel panic or system crash. The fix involves moving the connector assignment into atomic_enable() and using drm_atomic_get_new_connector_for_encoder() to correctly retrieve the connector from the atomic state, preventing the NULL pointer dereference. This vulnerability affects Linux kernel versions containing the affected commit hashes referenced, primarily impacting devices using the MSM DPU driver for display rendering. No known exploits are reported in the wild as of the publication date (September 11, 2024).
Potential Impact
For European organizations, the impact of CVE-2024-45015 depends on the deployment of Linux systems running kernels with the vulnerable MSM DPU driver, which is predominantly found in devices using Qualcomm Snapdragon SoCs, such as smartphones, embedded systems, and some IoT devices. Enterprises relying on Linux-based embedded devices for critical operations, including telecommunications infrastructure, industrial control systems, or mobile device fleets, could experience system crashes or denial of service due to kernel panics triggered by this vulnerability. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting denial of service can disrupt business continuity, especially in environments where uptime is critical. Additionally, devices that rely on graphical output or display rendering may become unresponsive, impacting user operations or monitoring capabilities. Given the absence of known exploits, the immediate threat level is moderate; however, the potential for future exploitation exists if attackers develop triggers for the NULL pointer dereference. European organizations with embedded Linux devices or mobile device management responsibilities should be vigilant, as disruption in these systems could affect sectors like manufacturing, telecommunications, and public services.
Mitigation Recommendations
To mitigate CVE-2024-45015, organizations should: 1) Identify and inventory all Linux-based devices using Qualcomm MSM DPU drivers, particularly those running kernels with the affected commit hashes. 2) Apply the official Linux kernel patches that move the connector assignment to atomic_enable() and correctly retrieve the connector from the atomic state, as referenced in the patchwork link (https://patchwork.freedesktop.org/patch/606729/). 3) For devices where kernel patching is not immediately feasible, consider implementing kernel-level monitoring to detect and alert on kernel NULL pointer dereferences or crashes related to the DRM subsystem. 4) Engage with device vendors and OEMs to obtain updated firmware or kernel versions incorporating the fix. 5) Implement robust device management policies to ensure timely updates and minimize exposure. 6) Test patches in controlled environments before deployment to avoid unintended disruptions. 7) Monitor security advisories for any emerging exploit developments related 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
- 2024-08-21T05:34:56.682Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9826c4522896dcbe0eda
Added to database: 5/21/2025, 9:08:54 AM
Last enriched: 6/28/2025, 11:55:40 PM
Last updated: 8/12/2025, 11:54:04 AM
Views: 13
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
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.