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-2024-49848: CWE-416 Use After Free in Qualcomm, Inc. Snapdragon

0
Medium
VulnerabilityCVE-2024-49848cvecve-2024-49848cwe-416
Published: Mon Apr 07 2025 (04/07/2025, 10:15:50 UTC)
Source: CVE Database V5
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

Memory corruption while processing multiple IOCTL calls from HLOS to DSP.

AI-Powered Analysis

AILast updated: 02/26/2026, 19:44:03 UTC

Technical Analysis

CVE-2024-49848 is a use-after-free vulnerability classified under CWE-416 found in Qualcomm Snapdragon chipsets. The vulnerability occurs due to improper memory management when handling multiple IOCTL (Input/Output Control) calls from the High-Level Operating System (HLOS) to the Digital Signal Processor (DSP). Specifically, the flaw leads to memory corruption by freeing memory prematurely and then accessing it, which can cause unpredictable behavior including crashes, data corruption, or arbitrary code execution. The affected products span a broad spectrum of Qualcomm hardware, including numerous Snapdragon mobile platforms (from Snapdragon 4 Gen 1 to Snapdragon 8+ Gen 2), FastConnect wireless subsystems, modem-RF systems, automotive platforms, wearable platforms, and various connectivity chips. Exploitation requires the attacker to have high-level privileges on the device, as the attack vector involves sending crafted IOCTL calls locally. No user interaction is needed, but the attacker must already have elevated access, which limits remote exploitation but does not eliminate risk from local attackers or malicious applications with escalated privileges. The vulnerability impacts confidentiality, integrity, and availability, potentially allowing attackers to execute arbitrary code or cause denial of service. Although no public exploits are known, the broad product impact and critical nature of Snapdragon components in mobile and embedded devices make this a significant concern. The CVSS v3.1 score of 6.7 reflects medium severity, balancing the high impact with the requirement for privileged access and local exploitation. No patches have been released yet, so mitigation relies on access control and monitoring.

Potential Impact

This vulnerability can have severe consequences for organizations and individuals relying on affected Qualcomm Snapdragon-based devices. Successful exploitation could allow attackers to execute arbitrary code with high privileges, leading to full device compromise. This threatens confidentiality by exposing sensitive data, integrity by allowing unauthorized modifications, and availability by causing crashes or denial of service. The vulnerability affects a wide range of devices including smartphones, tablets, IoT devices, automotive systems, and wearables, potentially impacting millions of endpoints globally. Enterprises using Snapdragon-powered devices for critical communications or operational technology could face operational disruptions and data breaches. The requirement for local privileged access reduces the risk of remote exploitation but increases the threat from insider attacks, malicious apps with escalated privileges, or compromised supply chains. The lack of patches increases exposure time, and the complexity of the affected hardware ecosystem complicates mitigation and detection efforts.

Mitigation Recommendations

1. Monitor Qualcomm and device vendors for official patches and apply them promptly once available. 2. Restrict and tightly control privileged access on devices to prevent unauthorized users or applications from issuing IOCTL calls to the DSP. 3. Employ application whitelisting and privilege separation to minimize the risk of privilege escalation that could enable exploitation. 4. Implement runtime integrity monitoring and anomaly detection to identify unusual IOCTL call patterns or memory corruption symptoms. 5. For enterprise-managed devices, enforce strict device management policies including disabling unnecessary services and interfaces that could be leveraged to issue IOCTL calls. 6. Collaborate with hardware and OS vendors to ensure that future firmware and driver updates include enhanced validation and memory management safeguards for IOCTL handling. 7. Conduct regular security audits and penetration testing focusing on local privilege escalation vectors and DSP interactions. 8. Educate users and administrators about the risks of installing untrusted applications that might attempt to exploit this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
qualcomm
Date Reserved
2024-10-20T17:18:43.218Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69a0a1b985912abc71d0a0e1

Added to database: 2/26/2026, 7:40:41 PM

Last enriched: 2/26/2026, 7:44:03 PM

Last updated: 2/26/2026, 11:16:37 PM

Views: 3

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses