CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
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. |
Memory corruption in Audio while processing the VOC packet data from ADSP. |
Transient DOS during hypervisor virtual I/O operation in a virtual machine. |
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. |
While processing the authentication message in UE, improper authentication may lead to information disclosure. |
Memory corruption in Kernel while parsing metadata. |
Transient DOS while parsing a vender specific IE (Information Element) of reassociation response management frame. |
Memory corruption when two threads try to map and unmap a single node simultaneously. |
Memory corruption while triggering commands in the PlayReady Trusted application. |
Memory corruption while processing a QMI request for allocating memory from a DHMS supported subsystem. |
Transient DOS while key unwrapping process, when the given encrypted key is empty or NULL. |
Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling. |
Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur. |
Improper Access to the VM resource manager can lead to Memory Corruption. |
Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers. |
Memory Corruption in HLOS while importing a cryptographic key into KeyMaster Trusted Application. |
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 |