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

0
High
VulnerabilityCVE-2025-21444cvecve-2025-21444cwe-120
Published: Tue Jul 08 2025 (07/08/2025, 12:48:54 UTC)
Source: CVE Database V5
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

Memory corruption while copying the result to the transmission queue in EMAC.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 20:49:16 UTC

Technical Analysis

CVE-2025-21444 is a classic buffer overflow vulnerability categorized under CWE-120, discovered in the Qualcomm Snapdragon chipset family. The vulnerability occurs due to a failure to properly check the size of input data when copying the result to the transmission queue within the Ethernet Media Access Controller (EMAC) component. This memory corruption flaw can be triggered by a local attacker with limited privileges (PR:L) and does not require user interaction (UI:N). The attack vector is local (AV:L), meaning the attacker must have some level of access to the device. The vulnerability affects a wide range of Snapdragon models, including QAM and SA series chips commonly found in smartphones, IoT devices, and embedded systems. Exploiting this vulnerability could allow an attacker to execute arbitrary code, escalate privileges, or cause a denial of service by corrupting memory structures critical to network transmission. The CVSS v3.1 base score is 7.8, reflecting high impact on confidentiality, integrity, and availability. Although no known exploits have been reported in the wild, the ease of exploitation combined with the broad deployment of affected chipsets makes this a significant threat. Qualcomm has not yet released patches, so mitigation currently relies on limiting local access and monitoring.

Potential Impact

The impact of CVE-2025-21444 is substantial for organizations relying on Qualcomm Snapdragon chipsets in their devices. Successful exploitation can lead to arbitrary code execution, allowing attackers to gain elevated privileges or control over affected devices. This compromises confidentiality by potentially exposing sensitive data, integrity by altering system or network operations, and availability by causing device crashes or denial of service. Given the widespread use of Snapdragon processors in mobile phones, IoT devices, and embedded systems, the vulnerability could affect a large number of endpoints globally. Organizations in sectors such as telecommunications, critical infrastructure, and consumer electronics may face operational disruptions and increased risk of targeted attacks. The local attack vector limits remote exploitation but insider threats or malware with local access could leverage this flaw. The absence of known exploits currently reduces immediate risk but also means organizations must proactively prepare for potential future attacks once exploit code becomes available.

Mitigation Recommendations

To mitigate CVE-2025-21444, organizations should implement the following specific measures: 1) Monitor Qualcomm’s advisories closely and apply official patches immediately upon release to affected Snapdragon chipsets. 2) Restrict local access to devices running vulnerable Snapdragon processors by enforcing strict access controls and user privilege management to prevent untrusted users from executing local code. 3) Deploy host-based intrusion detection systems (HIDS) and endpoint monitoring solutions to detect anomalous behavior indicative of exploitation attempts, such as unexpected memory corruption or network transmission anomalies. 4) For embedded and IoT devices, implement secure boot and runtime integrity checks to prevent unauthorized code execution. 5) Conduct regular security audits and vulnerability assessments focusing on local privilege escalation vectors. 6) Educate users and administrators about the risks of local exploitation and the importance of limiting physical and logical access to devices. 7) In environments where patching is delayed, consider network segmentation to isolate vulnerable devices and reduce the attack surface. These targeted mitigations go beyond generic advice by focusing on the local attack vector and the specific nature of the EMAC transmission queue buffer overflow.

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

Technical Details

Data Version
5.1
Assigner Short Name
qualcomm
Date Reserved
2024-12-18T09:50:08.922Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 686d15066f40f0eb72f50f83

Added to database: 7/8/2025, 12:54:30 PM

Last enriched: 2/26/2026, 8:49:16 PM

Last updated: 3/25/2026, 2:59:03 AM

Views: 72

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 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