EUVD-2025-210020
GHSA-rjww-f3q9-7g2w
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (qualcomm) · only source for this CVE.
CVSS VectorVendor: qualcomm
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
1DescriptionCVE.org
Memory Corruption when processing device identifier strings that exceed the expected maximum length.
AnalysisAI
Local privilege escalation via memory corruption in Qualcomm Snapdragon platform components allows an authenticated low-privileged local attacker to corrupt memory by supplying device identifier strings exceeding the expected maximum length. The CVSS 7.8 (AV:L/AC:L/PR:L) profile combined with CWE-787 out-of-bounds write indicates a classic stack/heap overflow path that can be leveraged for code execution with full confidentiality, integrity, and availability impact on affected devices. No public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Technical ContextAI
The flaw resides in Qualcomm Snapdragon platform software (per CPE cpe:2.3:a:qualcomm,_inc.:snapdragon) which underpins mobile SoCs widely deployed in Android handsets, automotive, IoT and connectivity products. The root cause class is CWE-787 (Out-of-bounds Write): firmware code parsing device identifier strings lacks a proper length check against a fixed-size destination buffer, so an oversized identifier overflows adjacent memory. Because Snapdragon components often run in privileged contexts (kernel drivers, TrustZone/QSEE trustlets, modem firmware), a write-out-of-bounds primitive here can corrupt control data structures and pivot into arbitrary code execution within the affected component's privilege domain.
RemediationAI
Apply the patch published in the Qualcomm June 2026 Security Bulletin (https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2026-bulletin.html); exact fixed component versions are listed there and should be matched against the Snapdragon parts in your fleet. For mobile devices, this means installing the next OEM Android security patch level that incorporates the Qualcomm closed-source component fix, and for embedded/automotive integrators it means consuming the updated Qualcomm BSP and re-flashing affected units. If patching is delayed, compensating controls include restricting sideloading and enforcing strict app vetting (since exploitation requires local code execution as a low-privileged user), enabling Google Play Protect or equivalent runtime app scanning, and minimizing exposure of attack surfaces such as debug interfaces or third-party apps that interact with device identifier APIs; note these controls reduce but do not eliminate risk, since any compromised app context could still trigger the overflow.
More in Snapdragon
View allMemory corruption in Qualcomm Snapdragon Wi-Fi/NAN firmware allows an attacker within wireless range to overflow a stack
Buffer overflow in Qualcomm Snapdragon firmware enables authentication bypass on adjacent networks, allowing remote unau
Local privilege escalation and memory corruption in Qualcomm Snapdragon WLAN firmware occurs when the driver parses malf
Memory corruption in Qualcomm Snapdragon Strongbox component allows local low-privileged attackers to trigger a buffer o
Local privilege escalation in Qualcomm Snapdragon chipsets stems from an out-of-bounds memory access in the Strongbox tr
Memory corruption in Qualcomm Snapdragon chipsets allows adjacent network attackers to achieve arbitrary code execution
Bootloader integrity bypass in Qualcomm Snapdragon platforms allows a high-privileged local attacker to write to a speci
Authentication bypass in Qualcomm Snapdragon SoCs allows adjacent network attackers to exploit a cryptographic flaw duri
Memory corruption in Qualcomm Snapdragon IOCTL device driver handling enables a local low-privilege attacker to achieve
Memory corruption in Qualcomm Snapdragon's fingerprint Trusted Application (TA) allows a local low-privileged attacker t
Memory corruption in Qualcomm Snapdragon platforms occurs when a packet with a size value near the maximum allowable lim
Local privilege escalation via memory corruption affects Qualcomm Snapdragon platforms, where allocating memory with siz
Same weakness CWE-787 – Out-of-bounds Write
View allSame technique Memory Corruption
View allShare
External POC / Exploit Code
Leaving vuln.today