| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption due to integer overflow or wraparound in Core while DDR memory assignment. |
| Memory corruption in modem due to stack based buffer overflow while parsing OTASP Key Generation Request Message. |
| Memory corruption in Core due to time-of-check time-of-use race condition during dump collection in trust zone. |
| Transient DOS due to reachable assertion in Modem while processing SIB1 Message. |
| Transient DOS due to reachable assertion in Modem because of invalid network configuration. |
| Transient DOS due to reachable assertion in modem when network repeatedly sent invalid message container for NR to LTE handover. |
| Memory corruption in User Identity Module due to integer overflow to buffer overflow when a segement is received via qmi http. |
| Transient DOS due to reachable assertion in modem during MIB reception and SIB timeout |
| Memory corruption due to configuration weakness in modem wile sending command to write protected files. |
| Memory corruption due to buffer copy without checking size of input while running memory sharing tests with large scattered memory. |
| Memory corruption due to double free in core while initializing the encryption key. |
| Memory corruption in modem due to buffer overflow while processing a PPP packet |
| Memory corruption in modem due to integer overflow to buffer overflow while handling APDU response |
| information disclosure due to cryptographic issue in Core during RPMB read request. |
| Assertion occurs while processing Reconfiguration message due to improper validation |
| Improper access control sequence for AC database after memory allocation can lead to possible memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking |
| Reading PRNG output may lead to improper key generation due to lack of buffer validation in Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking |
| Improper validation of memory region in Hypervisor can lead to incorrect region mapping in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking |
| Possible unauthorized access to secure space due to improper check of data allowed while flashing the no access control device configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking |
| Possible access control violation while setting current permission for VMIDs due to improper permission masking in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking |
