Skip to main content

CVE-2022-49467: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2022-49467cvecve-2022-49467
Published: Wed Feb 26 2025 (02/26/2025, 02:13:12 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: drm: msm: fix possible memory leak in mdp5_crtc_cursor_set() drm_gem_object_lookup will call drm_gem_object_get inside. So cursor_bo needs to be put when msm_gem_get_and_pin_iova fails.

AI-Powered Analysis

AILast updated: 06/30/2025, 15:57:23 UTC

Technical Analysis

CVE-2022-49467 is a vulnerability identified in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically within the msm (Qualcomm Snapdragon) driver component. The issue pertains to a potential memory leak in the function mdp5_crtc_cursor_set(). The vulnerability arises because drm_gem_object_lookup internally calls drm_gem_object_get, which increments the reference count of a graphics memory object (cursor_bo). However, if the subsequent call msm_gem_get_and_pin_iova fails, the code does not properly release the reference to cursor_bo, leading to a memory leak. This leak could cause gradual consumption of kernel memory resources, potentially degrading system performance or stability over time. Although this vulnerability does not directly enable code execution or privilege escalation, the improper resource management in a critical graphics subsystem could be exploited in scenarios where attackers aim to cause denial of service (DoS) by exhausting kernel memory. The vulnerability affects specific Linux kernel versions identified by the commit hash e172d10a9c4acc69bb07cbe9142ded2df791ff1f, indicating a particular snapshot of the kernel source. The issue has been publicly disclosed but no known exploits are currently reported in the wild. The patch involves ensuring that the cursor_bo reference is properly released when msm_gem_get_and_pin_iova fails, preventing the leak. This vulnerability is relevant primarily to systems running Linux kernels with the affected msm driver, commonly found in devices using Qualcomm Snapdragon chipsets, including embedded and mobile platforms that run Linux-based operating systems.

Potential Impact

For European organizations, the impact of CVE-2022-49467 depends largely on their deployment of Linux systems utilizing the affected msm driver, which is typical in devices with Qualcomm Snapdragon SoCs. Enterprises relying on embedded Linux devices, IoT infrastructure, or mobile devices running custom Linux kernels with this driver could experience degraded system stability or performance due to memory leaks. Over time, this could lead to system crashes or denial of service conditions, impacting availability of critical services. While the vulnerability does not directly compromise confidentiality or integrity, the potential for DoS could disrupt operations, especially in industrial control systems, telecommunications, or edge computing environments prevalent in Europe. Organizations with large-scale deployments of such devices may face increased maintenance overhead and risk of operational interruptions. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed proactively to avoid future exploitation or inadvertent system failures.

Mitigation Recommendations

To mitigate CVE-2022-49467, European organizations should: 1) Identify all Linux systems running kernels with the affected msm driver, focusing on devices with Qualcomm Snapdragon chipsets. 2) Apply the official Linux kernel patches that fix the memory leak in mdp5_crtc_cursor_set(), ensuring the cursor_bo reference is properly released on failure paths. 3) If immediate patching is not feasible, implement monitoring of kernel memory usage and system logs for signs of memory leaks or instability related to the DRM subsystem. 4) For embedded or mobile devices, coordinate with hardware vendors or device manufacturers to obtain updated firmware or kernel versions incorporating the fix. 5) Incorporate this vulnerability into vulnerability management and patching workflows, prioritizing updates for critical infrastructure devices. 6) Conduct regression testing post-patching to confirm system stability and absence of memory leaks. 7) Limit exposure by restricting untrusted user access to vulnerable systems, as exploitation requires interaction with the graphics subsystem. These targeted steps go beyond generic advice by focusing on the specific driver, device types, and operational contexts relevant to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-02-26T02:08:31.577Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d982ec4522896dcbe5b1c

Added to database: 5/21/2025, 9:09:02 AM

Last enriched: 6/30/2025, 3:57:23 PM

Last updated: 7/31/2025, 2:57:19 PM

Views: 14

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