Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-47314: CWE-20 Improper Input Validation in Qualcomm, Inc. Snapdragon

0
High
VulnerabilityCVE-2025-47314cvecve-2025-47314cwe-20
Published: Wed Sep 24 2025 (09/24/2025, 15:33:46 UTC)
Source: CVE Database V5
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

Memory corruption while processing data sent by FE driver.

AI-Powered Analysis

AILast updated: 10/02/2025, 01:13:23 UTC

Technical Analysis

CVE-2025-47314 is a high-severity vulnerability affecting multiple Qualcomm Snapdragon chipsets, specifically versions including QAM8255P through SRV1M series. The root cause is improper input validation (CWE-20) in the processing of data sent by the Front-End (FE) driver, which leads to memory corruption. This memory corruption can result in severe consequences such as arbitrary code execution, privilege escalation, or denial of service. The vulnerability has a CVSS v3.1 base score of 7.8, indicating high severity, with an attack vector classified as local (AV:L), low attack complexity (AC:L), requiring low privileges (PR:L), and no user interaction (UI:N). The impact affects confidentiality, integrity, and availability (all rated high). The scope remains unchanged (S:U), meaning the vulnerability affects the vulnerable component only. The vulnerability is currently not known to be exploited in the wild, and no patches have been linked yet. Qualcomm Snapdragon chipsets are widely used in mobile devices, embedded systems, and IoT devices, making this vulnerability significant for any device relying on these affected chipsets. The improper input validation flaw suggests that malicious or malformed data sent to the FE driver can corrupt memory, potentially allowing attackers with local access to execute arbitrary code or disrupt device operation. Given the low privilege requirement and no user interaction needed, exploitation could be feasible in scenarios where an attacker has local access or can trick a process into sending malicious data to the FE driver.

Potential Impact

For European organizations, the impact of this vulnerability can be substantial, especially those relying on devices powered by affected Qualcomm Snapdragon chipsets. This includes smartphones, tablets, embedded systems in industrial control, automotive telematics, and IoT devices used in critical infrastructure. Exploitation could lead to unauthorized access to sensitive data, disruption of services, or compromise of device integrity. In sectors such as finance, healthcare, and critical infrastructure, this could translate into data breaches, operational downtime, or safety risks. Additionally, given the widespread use of Snapdragon chipsets in consumer devices, enterprises with bring-your-own-device (BYOD) policies may face indirect risks through compromised employee devices. The local attack vector limits remote exploitation but does not eliminate risk in environments where attackers can gain local access, such as through insider threats, compromised applications, or physical access to devices. The absence of known exploits in the wild provides a window for mitigation, but the high severity score demands prompt attention.

Mitigation Recommendations

1. Immediate inventory and identification of devices using the affected Snapdragon chipsets within the organization. 2. Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing CVE-2025-47314 and apply them promptly upon release. 3. Restrict local access to devices running vulnerable chipsets, enforcing strict physical security and access controls. 4. Employ endpoint detection and response (EDR) solutions to monitor for anomalous behavior indicative of exploitation attempts targeting FE driver interactions. 5. Limit the privileges of processes and users that can interact with the FE driver to reduce the attack surface. 6. For embedded and IoT devices, ensure secure boot and integrity verification mechanisms are in place to detect unauthorized code execution. 7. Educate staff about the risks of local exploitation and enforce policies to prevent unauthorized device usage or installation of untrusted applications that could trigger the vulnerability. 8. Consider network segmentation to isolate vulnerable devices from critical systems to contain potential compromises.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 68d41181d0cbc63b6d41b287

Added to database: 9/24/2025, 3:42:57 PM

Last enriched: 10/2/2025, 1:13:23 AM

Last updated: 10/7/2025, 1:50:49 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 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