CVE-2024-44982: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails If the dpu_format_populate_layout() fails, then FB is prepared, but not cleaned up. This ends up leaking the pin_count on the GEM object and causes a splat during DRM file closure: msm_obj->pin_count WARNING: CPU: 2 PID: 569 at drivers/gpu/drm/msm/msm_gem.c:121 update_lru_locked+0xc4/0xcc [...] Call trace: update_lru_locked+0xc4/0xcc put_pages+0xac/0x100 msm_gem_free_object+0x138/0x180 drm_gem_object_free+0x1c/0x30 drm_gem_object_handle_put_unlocked+0x108/0x10c drm_gem_object_release_handle+0x58/0x70 idr_for_each+0x68/0xec drm_gem_release+0x28/0x40 drm_file_free+0x174/0x234 drm_release+0xb0/0x160 __fput+0xc0/0x2c8 __fput_sync+0x50/0x5c __arm64_sys_close+0x38/0x7c invoke_syscall+0x48/0x118 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x4c/0x120 el0t_64_sync_handler+0x100/0x12c el0t_64_sync+0x190/0x194 irq event stamp: 129818 hardirqs last enabled at (129817): [<ffffa5f6d953fcc0>] console_unlock+0x118/0x124 hardirqs last disabled at (129818): [<ffffa5f6da7dcf04>] el1_dbg+0x24/0x8c softirqs last enabled at (129808): [<ffffa5f6d94afc18>] handle_softirqs+0x4c8/0x4e8 softirqs last disabled at (129785): [<ffffa5f6d94105e4>] __do_softirq+0x14/0x20 Patchwork: https://patchwork.freedesktop.org/patch/600714/
AI Analysis
Technical Summary
CVE-2024-44982 is a vulnerability identified in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically within the msm (Qualcomm Snapdragon) driver component responsible for managing the Display Processing Unit (DPU). The issue arises in the function dpu_format_populate_layout(), which is responsible for setting up the framebuffer (FB) layout for graphics rendering. If this function fails, the framebuffer is partially prepared but not properly cleaned up, leading to a resource leak of the pin_count on the Graphics Execution Manager (GEM) object. The pin_count tracks how many references or 'pins' are held on a GEM object to prevent it from being freed prematurely. Failure to decrement this count correctly results in a stale reference that causes a kernel warning and ultimately a kernel panic (splat) during the closure of the DRM file descriptor. This is evidenced by the kernel warning trace involving msm_gem_free_object and drm_gem_object_release_handle functions, culminating in a crash during the file release process. The vulnerability is rooted in improper error handling and resource management in the DRM msm driver, which can destabilize the kernel and cause denial of service (DoS) conditions. The issue affects Linux kernel versions containing the specified commit hashes and has been patched as per the linked patchwork submission. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with the affected msm DRM driver, commonly found on devices using Qualcomm Snapdragon chipsets, including embedded systems, mobile devices, and some specialized Linux distributions. The impact is mainly a denial of service due to kernel crashes triggered by malformed or unexpected graphics operations that cause the framebuffer setup to fail and leak resources. This could disrupt critical services relying on graphical output or GPU acceleration, such as industrial control systems, digital signage, or embedded devices in telecommunications infrastructure. While the vulnerability does not directly enable privilege escalation or data leakage, the resulting kernel panic could cause system downtime, impacting availability and operational continuity. Organizations with Linux-based infrastructure in sectors like manufacturing, telecom, or automotive that use Qualcomm-based hardware are particularly at risk. The absence of known exploits suggests limited immediate threat, but the potential for targeted attacks or accidental crashes remains.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernels to the latest patched versions that include the fix for CVE-2024-44982. Specifically, ensure that the DRM msm driver is updated to incorporate the cleanup logic for framebuffer preparation failures. For embedded or specialized devices where kernel updates are less frequent, consider applying backported patches from the official patchwork submission or vendor advisories. Additionally, implement monitoring for kernel warnings related to drm/msm and GEM objects to detect early signs of exploitation or instability. Restrict access to systems with vulnerable kernels to trusted users and processes to minimize the risk of triggering the flaw. In environments where kernel panics could cause significant disruption, deploy redundancy and failover mechanisms to maintain service availability. Finally, engage with hardware and OS vendors to confirm the status of this patch in their distributions and firmware updates.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-44982: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails If the dpu_format_populate_layout() fails, then FB is prepared, but not cleaned up. This ends up leaking the pin_count on the GEM object and causes a splat during DRM file closure: msm_obj->pin_count WARNING: CPU: 2 PID: 569 at drivers/gpu/drm/msm/msm_gem.c:121 update_lru_locked+0xc4/0xcc [...] Call trace: update_lru_locked+0xc4/0xcc put_pages+0xac/0x100 msm_gem_free_object+0x138/0x180 drm_gem_object_free+0x1c/0x30 drm_gem_object_handle_put_unlocked+0x108/0x10c drm_gem_object_release_handle+0x58/0x70 idr_for_each+0x68/0xec drm_gem_release+0x28/0x40 drm_file_free+0x174/0x234 drm_release+0xb0/0x160 __fput+0xc0/0x2c8 __fput_sync+0x50/0x5c __arm64_sys_close+0x38/0x7c invoke_syscall+0x48/0x118 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x4c/0x120 el0t_64_sync_handler+0x100/0x12c el0t_64_sync+0x190/0x194 irq event stamp: 129818 hardirqs last enabled at (129817): [<ffffa5f6d953fcc0>] console_unlock+0x118/0x124 hardirqs last disabled at (129818): [<ffffa5f6da7dcf04>] el1_dbg+0x24/0x8c softirqs last enabled at (129808): [<ffffa5f6d94afc18>] handle_softirqs+0x4c8/0x4e8 softirqs last disabled at (129785): [<ffffa5f6d94105e4>] __do_softirq+0x14/0x20 Patchwork: https://patchwork.freedesktop.org/patch/600714/
AI-Powered Analysis
Technical Analysis
CVE-2024-44982 is a vulnerability identified in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically within the msm (Qualcomm Snapdragon) driver component responsible for managing the Display Processing Unit (DPU). The issue arises in the function dpu_format_populate_layout(), which is responsible for setting up the framebuffer (FB) layout for graphics rendering. If this function fails, the framebuffer is partially prepared but not properly cleaned up, leading to a resource leak of the pin_count on the Graphics Execution Manager (GEM) object. The pin_count tracks how many references or 'pins' are held on a GEM object to prevent it from being freed prematurely. Failure to decrement this count correctly results in a stale reference that causes a kernel warning and ultimately a kernel panic (splat) during the closure of the DRM file descriptor. This is evidenced by the kernel warning trace involving msm_gem_free_object and drm_gem_object_release_handle functions, culminating in a crash during the file release process. The vulnerability is rooted in improper error handling and resource management in the DRM msm driver, which can destabilize the kernel and cause denial of service (DoS) conditions. The issue affects Linux kernel versions containing the specified commit hashes and has been patched as per the linked patchwork submission. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with the affected msm DRM driver, commonly found on devices using Qualcomm Snapdragon chipsets, including embedded systems, mobile devices, and some specialized Linux distributions. The impact is mainly a denial of service due to kernel crashes triggered by malformed or unexpected graphics operations that cause the framebuffer setup to fail and leak resources. This could disrupt critical services relying on graphical output or GPU acceleration, such as industrial control systems, digital signage, or embedded devices in telecommunications infrastructure. While the vulnerability does not directly enable privilege escalation or data leakage, the resulting kernel panic could cause system downtime, impacting availability and operational continuity. Organizations with Linux-based infrastructure in sectors like manufacturing, telecom, or automotive that use Qualcomm-based hardware are particularly at risk. The absence of known exploits suggests limited immediate threat, but the potential for targeted attacks or accidental crashes remains.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernels to the latest patched versions that include the fix for CVE-2024-44982. Specifically, ensure that the DRM msm driver is updated to incorporate the cleanup logic for framebuffer preparation failures. For embedded or specialized devices where kernel updates are less frequent, consider applying backported patches from the official patchwork submission or vendor advisories. Additionally, implement monitoring for kernel warnings related to drm/msm and GEM objects to detect early signs of exploitation or instability. Restrict access to systems with vulnerable kernels to trusted users and processes to minimize the risk of triggering the flaw. In environments where kernel panics could cause significant disruption, deploy redundancy and failover mechanisms to maintain service availability. Finally, engage with hardware and OS vendors to confirm the status of this patch in their distributions and firmware updates.
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.670Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9826c4522896dcbe0dce
Added to database: 5/21/2025, 9:08:54 AM
Last enriched: 6/28/2025, 11:25:24 PM
Last updated: 8/11/2025, 10:38:31 AM
Views: 12
Related Threats
CVE-2025-8864: CWE-532 Insertion of Sensitive Information into Log File in YugabyteDB Inc YugabyteDB Anywhere
MediumCVE-2025-8851: Stack-based Buffer Overflow in LibTIFF
MediumCVE-2025-8863: CWE-319 Cleartext Transmission of Sensitive Information in YugabyteDB Inc YugabyteDB
HighCVE-2025-8847: Cross Site Scripting in yangzongzhuan RuoYi
MediumCVE-2025-8839: Improper Authorization in jshERP
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.