EUVD-2025-209633Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Memory corruption when another driver calls an IOCTL with invalid input/output buffer.
AnalysisAI
Memory corruption in Qualcomm Snapdragon allows local authenticated attackers with low privileges to achieve arbitrary code execution and full system compromise. The vulnerability triggers when malicious drivers invoke specific IOCTLs with intentionally malformed input/output buffers, bypassing buffer validation checks. EPSS and KEV status not available at time of analysis; advisory references May 2026 bulletin suggesting pre-disclosure analysis.
Technical ContextAI
This vulnerability affects the IOCTL (Input/Output Control) interface in Qualcomm Snapdragon firmware or drivers, classified as CWE-822 (Untrusted Pointer Dereference). IOCTL handlers are kernel-mode interfaces that allow user-space applications and drivers to communicate with device drivers through control codes. The affected code fails to properly validate pointer references in buffer structures passed from calling drivers, leading to use of untrusted pointers that can corrupt kernel memory. The CPE string cpe:2.3:a:qualcomm,_inc.:snapdragon indicates broad exposure across the Snapdragon product line, which powers hundreds of millions of Android devices, automotive systems, IoT devices, and Windows-on-ARM laptops. The buffer overflow tag suggests the memory corruption may involve writing beyond allocated buffer boundaries during IOCTL processing.
RemediationAI
Apply security patches distributed through the Qualcomm Security Bulletin for May 2026 (https://docs.qualcomm.com/product/publicresources/securitybulletin/may-2026-bulletin.html), though the future bulletin date requires verification-check for May 2025 bulletin if May 2026 is unavailable. For Android devices, wait for OEM-specific security updates that incorporate Qualcomm patches, typically released 1-3 months after Qualcomm disclosure. Monitor your device manufacturer's security bulletin for specific Android Security Patch Level (ASPL) that addresses CVE-2025-47408. Until patches are available, implement defense-in-depth controls: restrict installation of third-party applications to trusted sources only using Android Enterprise management or similar MDM controls, enable Google Play Protect and verify it is active, disable USB debugging and ADB access on production devices, and enforce principle of least privilege for installed applications through permission reviews. On Android, utilize SELinux enforcing mode (default on modern versions) which may limit kernel exploitation impact through mandatory access controls. For embedded/IoT Snapdragon deployments, disable unused device drivers and IOCTL interfaces if platform allows selective driver loading, though this may impact functionality and requires extensive testing. Note that application sandboxing provides limited protection since the vulnerability exists at the kernel driver level, but reducing attack surface by minimizing installed software reduces exploitation vectors.
More in Snapdragon
View allBuffer 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
Local privilege escalation via memory corruption affects Qualcomm Snapdragon platforms, where allocating memory with siz
Use-after-free memory corruption in Qualcomm Snapdragon platform driver code allows a local low-privileged process to tr
Local privilege escalation via memory corruption affects a broad range of Qualcomm Snapdragon chipsets, where a use-afte
Local privilege escalation in Qualcomm Snapdragon platforms is possible through memory corruption when processing multip
Local privilege escalation in Qualcomm Snapdragon platforms stems from an out-of-bounds read (CWE-125) triggered during
Local privilege escalation and memory corruption in Qualcomm Snapdragon platforms allows an attacker with low-privileged
Same weakness CWE-822 – Untrusted Pointer Dereference
View allSame technique Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today