Snapdragon vulnerabilities
34 known vulnerabilities in Snapdragon from Qualcomm. 34 are rated high or critical, and 8 have been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.1 High severity
Snapdragon: Improper Verification of Cryptographic Signature
Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed.
- 7.0 High severity
Snapdragon: Buffer Over-read
Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions.
- 7.1 High severity
Snapdragon: Reusing a Nonce, Key Pair in Encryption
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
- 7.8 High severity
Snapdragon: Use After Free
Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization.
- 7.5 High severity
Snapdragon: Buffer Over-read
Transient DOS when receiving a service data frame with excessive length during device matching over a neighborhood awareness network protocol connection.
- 7.8 High severity
Qualcomm Multiple Chipsets Memory Corruption Exploited
Memory corruption while using alignments for memory allocation.
- 7.8 High severity
Snapdragon: Use After Free
Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocation of buffer resources.
- 8.2 High severity
Snapdragon: Buffer Over-read
Information disclosure while decoding RTP packet received by UE from the network, when payload length mentioned is greater than the available buffer length.
- 8.6 High severity
Qualcomm Multiple Chipsets Incorrect Authorization Exploited
Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.
- 7.5 High severity
Qualcomm Multiple Chipsets Use-After-Free Exploited
Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.
- 8.6 High severity
Qualcomm Multiple Chipsets Incorrect Authorization Exploited
Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.
- 7.8 High severity
Snapdragon: Out-of-bounds Write
Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer.
- 7.8 High severity
Snapdragon: Out-of-bounds Write
Memory corruption may occur when invoking IOCTL calls from userspace to the camera kernel driver to dump request information, due to a missing memory requirement check.
- 7.8 High severity
Snapdragon: Improper Restriction of Operations within the Bounds of a Memory Buffer
Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset.
- 7.8 High severity
Snapdragon: Use After Free
Memory corruption during voice activation, when sound model parameters are loaded from HLOS, and the received sound model list is empty in HLOS drive.
- 7.8 High severity
Snapdragon: Integer Overflow or Wraparound
Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image.
- 7.8 High severity
Snapdragon: Use After Free
Memory corruption can occur when process-specific maps are added to the global list. If a map is removed from the global list while another thread is using it for a process-specific task, issues may arise.
- 7.0 High severity
Snapdragon: Use After Free
Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer access.
- 7.8 High severity
Qualcomm Multiple Chipsets Use-After-Free Exploited
Memory corruption while maintaining memory maps of HLOS memory.
- 7.5 High severity
Snapdragon: Buffer Over-read
Transient DOS when processing the non-transmitted BSSID profile sub-elements present within the MBSSID Information Element (IE) of a beacon frame that is received from over-the-air (OTA).
- 7.8 High severity
Snapdragon: Use After Free
Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time.
- 7.5 High severity
Snapdragon: Improper Authentication
Cryptographic issue while performing attach with a LTE network, a rogue base station can skip the authentication phase and immediately send the Security Mode Command.
- 7.8 High severity
Snapdragon: Out-of-bounds Write
Memory corruption while processing the event ring, the context read pointer is untrusted to HLOS and when it is passed with arbitrary values, may point to address in the middle of ring element.
- 7.5 High severity
Snapdragon: Out-of-bounds Read
Transient DOS while parsing GATT service data when the total amount of memory that is required by the multiple services is greater than the actual size of the services buffer.
- 7.8 High severity
Snapdragon: Use After Free
Memory corruption while processing Listen Sound Model client payload buffer when there is a request for Listen Sound session get parameter from ST HAL.
- 7.0 High severity
Snapdragon: Concurrent Execution using Shared Resource with Improper Synchronization
The session index variable in PCM host voice audio driver initialized before PCM open, accessed during event callback from ADSP and reset during PCM close may lead to race condition between event callback - PCM close and reset session index causing memory corr
- 7.8 High severity
Qualcomm Multiple Chipsets Integer Overflow Exploited
Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.
- 7.8 High severity
Qualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset Exploited
Memory corruption while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.
- 7.8 High severity
Qualcomm Multiple Chipsets Use-After-Free Exploited
Memory corruption in DSP Services during a remote call from HLOS to DSP.
- 9.8 Critical severity
Snapdragon: Out-of-bounds Read
A malformed DLC can trigger Memory Corruption in SNPE library due to out of bounds read, such as by loading an untrusted model (e.g. from a remote source).
- 7.8 High severity
Snapdragon: Use After Free
In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used. So when a function called cam_mem_get_cpu_buf to get the kernel va to use, another thread can call CAM_REQ_MGR_RELEASE_BUF to unmap the kernel va which cause
- 7.0 High severity
Snapdragon: Time-of-check Time-of-use (TOCTOU) Race Condition
The buffer obtained from kernel APIs such as cam_mem_get_cpu_buf() may be readable/writable in userspace after kernel accesses it. In other words, user mode may race and modify the packet header (e.g. header.count), causing checks (e.g. size checks) in kernel
- 7.8 High severity
Snapdragon: Access of Resource Using Incompatible Type
The cam_get_device_priv function does not check the type of handle being returned (device/session/link). This would lead to invalid type usage if a wrong handle is passed to it.
- 7.8 High severity
Snapdragon: Incorrect Type Conversion or Cast
Memory corruption due to incorrect type conversion or cast in audio while using audio playback/capture when crafted address is sent from AGM IPC to AGM.