CVE-2022-49462: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. a6xx_gmu_init() passes the node to of_find_device_by_node() and of_dma_configure(), of_find_device_by_node() will takes its reference, of_dma_configure() doesn't need the node after usage. Add missing of_node_put() to avoid refcount leak.
AI Analysis
Technical Summary
CVE-2022-49462 is a vulnerability identified in the Linux kernel, specifically within the Direct Rendering Manager (DRM) subsystem for Qualcomm Adreno GPUs (a6xx series). The issue arises from a reference count leak in the function a6xx_gpu_init. The root cause is improper management of device tree node references: the function of_parse_phandle() returns a node pointer with an incremented reference count, which must be decremented using of_node_put() when the node is no longer needed. In the affected code path, a6xx_gmu_init() passes this node to of_find_device_by_node() and of_dma_configure(). While of_find_device_by_node() takes its own reference, of_dma_configure() does not require the node after use, but the missing call to of_node_put() leads to a reference count leak. Over time, this leak can cause resource exhaustion within the kernel's device tree node management, potentially leading to degraded system performance or instability. The vulnerability affects Linux kernel versions identified by the given commit hashes (all identical in the data), and no known exploits have been reported in the wild. The issue is primarily a resource management bug rather than a direct code execution or privilege escalation vulnerability. No CVSS score has been assigned yet, and no patches or exploit indicators are currently linked.
Potential Impact
For European organizations relying on Linux-based systems with Qualcomm Adreno a6xx GPUs—commonly found in embedded devices, mobile platforms, or specialized hardware—this vulnerability could lead to kernel resource leaks that degrade system stability or cause crashes. While it does not directly enable remote code execution or privilege escalation, prolonged exploitation or heavy usage scenarios could result in denial of service conditions due to resource exhaustion. This may affect critical infrastructure or industrial control systems using embedded Linux with these GPUs, causing operational disruptions. The impact on confidentiality and integrity is minimal, but availability could be impaired. Given the widespread use of Linux in servers, desktops, and embedded devices across Europe, organizations with hardware using affected GPU drivers should be aware. However, typical enterprise servers and desktops without this specific GPU hardware are unlikely to be affected. The lack of known exploits and the nature of the bug reduce immediate risk, but unpatched systems could face stability issues over time.
Mitigation Recommendations
Organizations should identify Linux systems running kernels with the affected a6xx DRM driver, particularly those using Qualcomm Adreno a6xx GPUs. Applying the official Linux kernel patches that add the missing of_node_put() calls to fix the reference count leak is the primary mitigation. If immediate patching is not feasible, monitoring system logs for kernel warnings or errors related to device tree node management and GPU initialization may help detect issues early. Limiting workload intensity on affected GPUs can reduce the risk of resource exhaustion. For embedded or specialized devices, coordinate with hardware vendors or Linux distribution maintainers to obtain updated kernel versions. Additionally, implementing kernel hardening and resource monitoring tools can help detect abnormal resource usage patterns. Regularly updating Linux kernels and drivers to the latest stable releases is recommended to incorporate this and other fixes.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland
CVE-2022-49462: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. a6xx_gmu_init() passes the node to of_find_device_by_node() and of_dma_configure(), of_find_device_by_node() will takes its reference, of_dma_configure() doesn't need the node after usage. Add missing of_node_put() to avoid refcount leak.
AI-Powered Analysis
Technical Analysis
CVE-2022-49462 is a vulnerability identified in the Linux kernel, specifically within the Direct Rendering Manager (DRM) subsystem for Qualcomm Adreno GPUs (a6xx series). The issue arises from a reference count leak in the function a6xx_gpu_init. The root cause is improper management of device tree node references: the function of_parse_phandle() returns a node pointer with an incremented reference count, which must be decremented using of_node_put() when the node is no longer needed. In the affected code path, a6xx_gmu_init() passes this node to of_find_device_by_node() and of_dma_configure(). While of_find_device_by_node() takes its own reference, of_dma_configure() does not require the node after use, but the missing call to of_node_put() leads to a reference count leak. Over time, this leak can cause resource exhaustion within the kernel's device tree node management, potentially leading to degraded system performance or instability. The vulnerability affects Linux kernel versions identified by the given commit hashes (all identical in the data), and no known exploits have been reported in the wild. The issue is primarily a resource management bug rather than a direct code execution or privilege escalation vulnerability. No CVSS score has been assigned yet, and no patches or exploit indicators are currently linked.
Potential Impact
For European organizations relying on Linux-based systems with Qualcomm Adreno a6xx GPUs—commonly found in embedded devices, mobile platforms, or specialized hardware—this vulnerability could lead to kernel resource leaks that degrade system stability or cause crashes. While it does not directly enable remote code execution or privilege escalation, prolonged exploitation or heavy usage scenarios could result in denial of service conditions due to resource exhaustion. This may affect critical infrastructure or industrial control systems using embedded Linux with these GPUs, causing operational disruptions. The impact on confidentiality and integrity is minimal, but availability could be impaired. Given the widespread use of Linux in servers, desktops, and embedded devices across Europe, organizations with hardware using affected GPU drivers should be aware. However, typical enterprise servers and desktops without this specific GPU hardware are unlikely to be affected. The lack of known exploits and the nature of the bug reduce immediate risk, but unpatched systems could face stability issues over time.
Mitigation Recommendations
Organizations should identify Linux systems running kernels with the affected a6xx DRM driver, particularly those using Qualcomm Adreno a6xx GPUs. Applying the official Linux kernel patches that add the missing of_node_put() calls to fix the reference count leak is the primary mitigation. If immediate patching is not feasible, monitoring system logs for kernel warnings or errors related to device tree node management and GPU initialization may help detect issues early. Limiting workload intensity on affected GPUs can reduce the risk of resource exhaustion. For embedded or specialized devices, coordinate with hardware vendors or Linux distribution maintainers to obtain updated kernel versions. Additionally, implementing kernel hardening and resource monitoring tools can help detect abnormal resource usage patterns. Regularly updating Linux kernels and drivers to the latest stable releases is recommended to incorporate this and other fixes.
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-02-26T02:08:31.576Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982ec4522896dcbe5ad9
Added to database: 5/21/2025, 9:09:02 AM
Last enriched: 6/30/2025, 7:40:41 AM
Last updated: 11/22/2025, 4:41:35 PM
Views: 31
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2023-30806: CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in Sangfor Net-Gen Application Firewall
CriticalCVE-2024-0401: CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in ASUS ExpertWiFi
HighCVE-2024-23690: CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in Netgear FVS336Gv3
HighCVE-2024-13976: CWE-427 Uncontrolled Search Path Element in Commvault Commvault for Windows
HighCVE-2024-12856: CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in Four-Faith F3x24
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.