Skip to main content

CVE-2021-47610: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2021-47610cvecve-2021-47610
Published: Wed Jun 19 2024 (06/19/2024, 14:57:59 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix null ptr access msm_ioctl_gem_submit() Fix the below null pointer dereference in msm_ioctl_gem_submit(): 26545.260705: Call trace: 26545.263223: kref_put+0x1c/0x60 26545.266452: msm_ioctl_gem_submit+0x254/0x744 26545.270937: drm_ioctl_kernel+0xa8/0x124 26545.274976: drm_ioctl+0x21c/0x33c 26545.278478: drm_compat_ioctl+0xdc/0xf0 26545.282428: __arm64_compat_sys_ioctl+0xc8/0x100 26545.287169: el0_svc_common+0xf8/0x250 26545.291025: do_el0_svc_compat+0x28/0x54 26545.295066: el0_svc_compat+0x10/0x1c 26545.298838: el0_sync_compat_handler+0xa8/0xcc 26545.303403: el0_sync_compat+0x188/0x1c0 26545.307445: Code: d503201f d503201f 52800028 4b0803e8 (b8680008) 26545.318799: Kernel panic - not syncing: Oops: Fatal exception

AI-Powered Analysis

AILast updated: 06/30/2025, 15:26:25 UTC

Technical Analysis

CVE-2021-47610 is a vulnerability identified in the Linux kernel specifically within the Direct Rendering Manager (DRM) subsystem for the MSM (Qualcomm Snapdragon) driver. The flaw is a null pointer dereference occurring in the function msm_ioctl_gem_submit(), which handles ioctl calls related to graphics memory submissions. The vulnerability manifests when the kernel attempts to dereference a null pointer, leading to a kernel panic and fatal exception, effectively causing a denial of service (DoS) condition. The provided call trace highlights the sequence of kernel functions leading to the crash, including kref_put, drm_ioctl_kernel, and compatibility ioctl handlers for ARM64 architectures. This vulnerability is rooted in improper handling of reference counts or object pointers in the MSM driver, which is part of the graphics stack for Qualcomm-based devices running Linux. Although no known exploits are currently reported in the wild, the vulnerability can be triggered by a local user or process issuing crafted ioctl calls to the DRM subsystem, potentially crashing the system or causing instability. The affected versions are identified by specific git commit hashes, indicating the vulnerability is present in certain kernel builds prior to the patch. No CVSS score has been assigned yet, and no patch links are provided in the data, but the issue has been officially published and enriched by CISA, indicating recognition by security authorities.

Potential Impact

For European organizations, the impact of CVE-2021-47610 primarily involves potential denial of service on Linux systems running kernels with the vulnerable MSM DRM driver. This is particularly relevant for organizations using Qualcomm Snapdragon-based embedded devices, IoT systems, or specialized Linux distributions on ARM64 platforms. A successful exploitation would cause kernel panics, leading to system crashes and downtime, which could disrupt critical services or operations relying on affected hardware. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting instability could be leveraged as part of a broader attack chain or cause operational disruptions in environments with high availability requirements. Given the widespread use of Linux in European enterprises, especially in telecommunications, manufacturing, and embedded systems, the vulnerability could affect devices in these sectors. However, the lack of known exploits and the requirement for local access or crafted ioctl calls somewhat limits the immediate risk to remote attackers. Nonetheless, organizations with devices running vulnerable kernels should consider this a medium-term risk to system reliability and availability.

Mitigation Recommendations

To mitigate CVE-2021-47610, European organizations should: 1) Identify and inventory all Linux systems running on Qualcomm Snapdragon MSM hardware or ARM64 platforms that include the DRM subsystem. 2) Apply the latest Linux kernel updates and patches that address this vulnerability as soon as they become available from trusted sources or vendor distributions. 3) Restrict access to device nodes associated with the DRM subsystem (e.g., /dev/dri/*) to trusted users and processes only, minimizing the risk of unauthorized ioctl calls. 4) Implement kernel hardening and security modules (such as SELinux or AppArmor) to limit the ability of unprivileged users to interact with kernel drivers. 5) Monitor system logs for kernel panics or unusual ioctl activity that could indicate attempted exploitation. 6) For embedded or IoT devices where kernel updates are challenging, consider network segmentation and strict access controls to reduce exposure. 7) Engage with hardware and software vendors to ensure timely patching and support for affected devices. These steps go beyond generic advice by focusing on access control to the vulnerable interface and proactive monitoring for exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-06-19T14:55:32.794Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9834c4522896dcbe95be

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

Last enriched: 6/30/2025, 3:26:25 PM

Last updated: 8/12/2025, 8:18:06 AM

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