CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur. |
Cryptographic issue in HLOS during key management. |
Transient DOS in Modem while allocating DSM items. |
Transient DOS while processing TIM IE from beacon frame as there is no check for IE length. |
Memory corruption while processing a QMI request for allocating memory from a DHMS supported subsystem. |
Memory Corruption in Audio while invoking callback function in driver from ADSP. |
Transient DOS in Multi-Mode Call Processor while processing UE policy container. |
Memory corruption when multiple listeners are being registered with the same file descriptor. |
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. |
Memory corruption when two threads try to map and unmap a single node simultaneously. |
Memory Corruption in WLAN HOST while processing WLAN FW request to allocate memory. |
Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call. |
Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions. |
Memory Corruption in WLAN HOST while parsing QMI response message from firmware. |
Transient DOS while parsing a vender specific IE (Information Element) of reassociation response management frame. |
Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper. |
Possible use after free due to improper handling of memory mapping of multiple processes simultaneously. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables |
Improper handling of address deregistration on failure can lead to new GPU address allocation failure. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables |
Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables |
Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music |