EUVD-2026-26989Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N/I:N/A:H
Lifecycle Timeline
4DescriptionCVE.org
Memory corruption while processing IOCTL command when device is in power-save state.
AnalysisAI
Memory corruption in Qualcomm Snapdragon SDK occurs when processing IOCTL commands while the device is in power-save state, allowing local authenticated attackers to trigger a denial of service. The vulnerability affects all versions of Snapdragon and requires local access with user-level privileges; no authentication bypass or privilege escalation is possible, but successful exploitation causes system crash or hang. EPSS and KEV status not provided; no public exploit code has been identified at time of analysis.
Technical ContextAI
The vulnerability involves improper memory handling in the IOCTL (input/output control) subsystem of Qualcomm Snapdragon, a widely deployed mobile system-on-chip (SoC) platform used in Android and other embedded devices. IOCTL commands are low-level system calls that allow applications to configure hardware and driver behavior. The root cause (CWE-749: Improperly Controlled Allocation of Insufficiently Sized Buffer) indicates that the code allocates or processes buffers without validating size constraints when the device is in a low-power state. Power-save modes alter clock and power states, potentially exposing race conditions or state-dependent buffer handling logic. The CPE string cpe:2.3:a:qualcomm,_inc.:snapdragon indicates the affected product is Snapdragon software/firmware; the wildcard version field suggests all publicly disclosed Snapdragon versions are in scope.
RemediationAI
Qualcomm is expected to release patched Snapdragon firmware and drivers via the May 2026 security bulletin (https://docs.qualcomm.com/product/publicresources/securitybulletin/may-2026-bulletin.html). Device manufacturers and carriers should apply these patches as soon as they are available for their respective Snapdragon platforms. Until patches are released or applied, organizations can implement mitigating controls: (1) Restrict local user access to IOCTL device interfaces via SELinux policies or AppArmor to trusted applications only - trade-off is reduced functionality for user applications. (2) Disable power-save features in high-security deployments by enforcing max performance mode, though this increases power consumption and heat. (3) Monitor system crash logs and reboot patterns to detect exploitation attempts. (4) Deploy mobile device management (MDM) to enforce security policies on corporate devices. Patch application is the primary remediation; workarounds are temporary and should not replace timely patching.
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-749 – Exposed Dangerous Method or Function
View allSame technique Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today