Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-47350: CWE-416 Use After Free in Qualcomm, Inc. Snapdragon

0
High
VulnerabilityCVE-2025-47350cvecve-2025-47350cwe-416
Published: Thu Dec 18 2025 (12/18/2025, 05:29:08 UTC)
Source: CVE Database V5
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

Memory corruption while handling concurrent memory mapping and unmapping requests from a user-space application.

AI-Powered Analysis

AILast updated: 12/18/2025, 06:06:29 UTC

Technical Analysis

CVE-2025-47350 is a use-after-free vulnerability classified under CWE-416, discovered in Qualcomm Snapdragon chipsets. The flaw occurs due to improper handling of concurrent memory mapping and unmapping requests issued by user-space applications, leading to memory corruption. This vulnerability affects a wide range of Snapdragon products, including FastConnect 6900 and 7800, WCD9378C, WCD9380, WCD9385, and several others, indicating a broad impact across multiple chipset versions and models. The vulnerability allows an attacker with low privileges (PR:L) to exploit the flaw without requiring user interaction (UI:N), potentially resulting in arbitrary code execution, privilege escalation, or denial of service by corrupting memory structures. The CVSS v3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) highlights that the attack vector is local, requires low complexity, and impacts confidentiality, integrity, and availability at a high level. Although no exploits are currently known in the wild, the vulnerability poses a significant risk to devices using affected Snapdragon chipsets, especially in environments where untrusted applications can run. The issue was reserved in May 2025 and published in December 2025, with Qualcomm as the assigner, but no patch links are currently available, indicating that mitigation may rely on forthcoming vendor updates. The vulnerability’s root cause is a race condition in memory management routines, which can be triggered by concurrent operations, a common challenge in complex SoC environments.

Potential Impact

For European organizations, the impact of CVE-2025-47350 is substantial, particularly for those relying on Snapdragon-based devices in mobile infrastructure, IoT deployments, or enterprise mobile endpoints. Exploitation could lead to unauthorized access to sensitive data, disruption of critical communications, and compromise of device integrity. Telecommunications providers using affected chipsets in network equipment or customer devices may face service outages or breaches. Enterprises with BYOD policies or mobile workforces using Snapdragon-powered smartphones and tablets risk lateral movement by attackers exploiting this vulnerability. The high confidentiality, integrity, and availability impact could result in data leaks, system manipulation, or denial of service, affecting business continuity and regulatory compliance under GDPR. The local attack vector means that attackers need some level of access, but this could be achieved through malicious apps or insider threats. The absence of known exploits currently provides a window for proactive mitigation, but the broad product impact and high severity necessitate urgent attention.

Mitigation Recommendations

European organizations should prioritize monitoring and controlling the installation and execution of user-space applications on Snapdragon-powered devices, enforcing strict application whitelisting and privilege restrictions to minimize the risk of local exploitation. Network segmentation and endpoint detection solutions should be enhanced to identify anomalous memory operations or suspicious behavior indicative of exploitation attempts. Organizations should maintain close communication with Qualcomm and device vendors to obtain and deploy security patches promptly once released. Until patches are available, applying device-level security controls such as disabling unnecessary services, restricting developer/debugging access, and employing runtime protections like memory corruption mitigations (e.g., ASLR, DEP) can reduce exploitation likelihood. Security teams should also conduct vulnerability assessments on devices in use to identify affected hardware and prioritize remediation. For mobile device management (MDM) platforms, enforcing strict update policies and restricting sideloading of untrusted applications will help mitigate attack vectors. Finally, incident response plans should be updated to include scenarios involving exploitation of this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
qualcomm
Date Reserved
2025-05-06T08:33:16.263Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6943963858cc240f07ac2f3a

Added to database: 12/18/2025, 5:50:48 AM

Last enriched: 12/18/2025, 6:06:29 AM

Last updated: 12/18/2025, 8:27:33 AM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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