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-47399: CWE-120 Buffer Copy Without Checking Size of Input ('Classic Buffer Overflow') in Qualcomm, Inc. Snapdragon

0
High
VulnerabilityCVE-2025-47399cvecve-2025-47399cwe-120
Published: Mon Feb 02 2026 (02/02/2026, 15:20:45 UTC)
Source: CVE Database V5
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

Memory Corruption while processing IOCTL call to update sensor property settings with invalid input parameters.

AI-Powered Analysis

AILast updated: 02/27/2026, 07:29:09 UTC

Technical Analysis

CVE-2025-47399 is a classic buffer overflow vulnerability (CWE-120) identified in Qualcomm Snapdragon chipsets, specifically triggered by processing IOCTL calls that update sensor property settings with invalid input parameters. The vulnerability arises because the affected code does not properly check the size of input data before copying it into a buffer, leading to memory corruption. This memory corruption can be exploited by a local attacker with low privileges to execute arbitrary code, escalate privileges, or cause denial of service by crashing the device. The affected Snapdragon versions include a broad range of modem and sensor-related chipsets such as Cologne, FastConnect 7800, WCD9378C, WSA8840 series, and several X-series variants, which are embedded in many mobile devices globally. The vulnerability requires local access and low privileges but does not require user interaction, increasing the risk in scenarios where an attacker gains limited device access. The CVSS v3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates that the attack vector is local, with low attack complexity and privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. No public exploits have been reported yet, but the vulnerability’s nature makes it a critical concern for device manufacturers, mobile carriers, and end users. Qualcomm has not yet released patches, but mitigation will likely involve firmware updates and improved input validation in the IOCTL handling code.

Potential Impact

The impact of CVE-2025-47399 is significant for organizations and individuals relying on Qualcomm Snapdragon-based devices. Successful exploitation can lead to arbitrary code execution at a privileged level, enabling attackers to bypass security controls, access sensitive data, manipulate device functionality, or cause persistent denial of service. This can compromise user privacy, disrupt critical communications, and undermine trust in mobile platforms. Enterprises using Snapdragon-powered devices for corporate communications or IoT deployments may face data breaches or operational outages. The vulnerability’s local attack vector means that attackers need some level of device access, which could be achieved through physical access, malicious apps exploiting other vulnerabilities, or insider threats. Given the widespread use of Snapdragon chipsets in smartphones, tablets, and IoT devices worldwide, the potential scale of impact is large. The lack of known exploits in the wild currently reduces immediate risk but also underscores the importance of proactive mitigation before attackers develop reliable exploit code.

Mitigation Recommendations

To mitigate CVE-2025-47399, organizations and device users should: 1) Monitor Qualcomm and device vendor advisories closely and apply firmware or software patches promptly once available. 2) Restrict local access to devices by enforcing strong device lock policies, disabling unnecessary debug interfaces, and limiting physical access. 3) Employ application whitelisting and privilege restrictions to reduce the risk of malicious code gaining local access. 4) Implement runtime protections such as stack canaries, address space layout randomization (ASLR), and control-flow integrity (CFI) where supported by the device firmware. 5) Conduct security audits of custom drivers or software interacting with sensor IOCTL interfaces to ensure proper input validation. 6) Educate users about the risks of installing untrusted applications that might facilitate local access. 7) For enterprises, consider network segmentation and endpoint detection to identify anomalous behavior indicative of exploitation attempts. These steps go beyond generic advice by focusing on limiting local access vectors and enhancing runtime defenses specific to the nature of this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

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

Threat ID: 6980c319f9fa50a62f48b5f3

Added to database: 2/2/2026, 3:30:33 PM

Last enriched: 2/27/2026, 7:29:09 AM

Last updated: 3/19/2026, 8:29:11 PM

Views: 50

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