Qualcomm

Possible null pointer dereference in thread cache operation handler due to lack of validation of user provided input in

Possible null pointer dereference in trap handler due to lack of thread ID validation before dereferencing it in Snapdra

Possible null pointer dereference in thread profile trap handler due to lack of thread ID validation before dereferencin

Possible null pointer dereference due to lack of TLB validation for user provided address in Snapdragon Auto, Snapdragon

Possible heap Memory Corruption Issue due to lack of input validation when sending HWTC IQ Capture command in Snapdragon

Possible integer overflow to buffer overflow due to improper input validation in FTM ARA commands in Snapdragon Auto, Sn

Improper validation of a socket state when socket events are being sent to clients can lead to invalid access of memory

Improper handling of resource allocation in virtual machines can lead to information exposure in Snapdragon Consumer IOT

Improper access control in TrustZone due to improper error handling while handling the signing key in Snapdragon Auto, S

An integer overflow due to improper check performed after the address and size passed are aligned in Snapdragon Compute,

Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Compute, Snapdr

Possible information exposure and denial of service due to NAS not dropping messages when integrity check fails in Snapd

Possible use after free due to improper memory validation when initializing new interface via Interface add command in S

Possible memory corruption due to improper validation of memory address while processing user-space IOCTL for clearing F

Possible use after free due improper validation of reference from call back to internal store table in Snapdragon Auto,

Possible race condition can occur due to lack of synchronization mechanism when On-Device Logging node open twice concur

Possible out of bound access due to improper validation of function table entries in Snapdragon Auto, Snapdragon Compute

Possible buffer overflow due to improper input validation in PDM DIAG command in FTM in Snapdragon Auto, Snapdragon Comp

Possible buffer overflow due to improper input validation in factory calibration and test DIAG command in Snapdragon Aut

Possible denial of service scenario due to improper input validation of received NAS OTA message in Snapdragon Auto, Sna

Possible buffer over read due to improper IE size check of Bearer capability IE in MT setup request from network in Snap

Possible buffer overflow due to improper validation of FTM command payload in Snapdragon Auto, Snapdragon Compute, Snapd

Possible heap overflow due to improper length check of domain while parsing the DNS response in Snapdragon Auto, Snapdra

A FTM Diag command can allow an arbitrary write into modem OS space in Snapdragon Auto, Snapdragon Compute, Snapdragon C

Information disclosure through timing and power side-channels during mod exponentiation for RSA-CRT in Snapdragon Auto,

Possible memory corruption due to Improper handling of hypervisor unmap operations for concurrent memory operations in S

Possible integer overflow can occur due to improper length check while calculating count and grace period in Snapdragon

Possible denial of service scenario can occur due to lack of length check on Channel Switch Announcement IE in beacon or

Possible out of bound memory access due to improper boundary check while creating HSYNC fence in Snapdragon Auto, Snapdr

Improper handling of sensor HAL structure in absence of sensor can lead to use after free in Snapdragon Auto

Improper authentication of sub-frames of a multicast AMSDU frame can lead to information disclosure in Snapdragon Auto,

Possible buffer overflow due to Improper validation of received CF-ACK and CF-Poll data frames in Snapdragon Auto, Snapd

Possible buffer over read due to improper buffer allocation for file length passed from user space in Snapdragon Auto, S

Possible out of bound access due to lack of validation of page offset before page is inserted in Snapdragon Auto, Snapdr

Possible buffer out of bound read can occur due to improper validation of TBTT count and length while parsing the beacon

Improper authentication of EAP WAPI EAPOL frames from unauthenticated user can lead to information disclosure in Snapdra

Possible out of bound read due to improper validation of packet length while handling data transfer in VR service in Sna

Possible memory corruption due to lack of validation of client data used for memory allocation in Snapdragon Auto, Snapd

Possible memory corruption due to lack of validation of client data used for memory allocation in Snapdragon Auto, Snapd

Possible stack overflow due to improper length check of TLV while copying the TLV to a local stack variable in Snapdrago

Possible buffer overflow due to improper size calculation of payload received in VR service in Snapdragon Auto, Snapdrag

Possible out of bound read or write in VR service due to lack of validation of DSP selection values in Snapdragon Comput

Possible stack overflow due to improper validation of camera name length before copying the name in VR Service in Snapdr

Possible buffer over read due to lack of data length check in QVR Service configuration in Snapdragon Auto, Snapdragon C

Possible buffer overflow due to improper validation of index value while processing the plugin block in Snapdragon Auto,

Possible buffer overflow due to improper handling of negative data length while processing write request in VR service i

Possible buffer over read due to lack of length check while parsing beacon IE response in Snapdragon Auto, Snapdragon Co

Possible buffer over read due to improper validation of frame length while processing AEAD decryption during ASSOC respo

Improper validation of kernel buffer address while copying information back to user buffer can lead to kernel memory inf

Improper validation of kernel buffer address while copying information back to user buffer can lead to kernel memory inf