| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption when multiple listeners are being registered with the same file descriptor. |
| Information disclosure when the trusted application metadata symbol addresses are accessed while loading an ELF in TEE. |
| Memory corruption when preparing a shared memory notification for a memparcel in Resource Manager. |
| Information disclosure when the ADSP payload size received in HLOS in response to Audio Stream Manager matrix session is less than this expected size. |
| Memory corruption in HLOS while checking for the storage type. |
| Memory corruption while validating the TID to Link Mapping action request frame, when a station connects to an access point. |
| Transient DOS while parse fils IE with length equal to 1. |
| Memory corruption while copying the result to the transmission queue which is shared between the virtual machine and the host. |
| Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node. |
| Memory corruption in Core when updating rollback version for TA and OTA feature is enabled. |
| Cryptographic issue in Automotive while unwrapping the key secs2d and verifying with RPMB data. |
| Memory corruption in HLOS while running playready use-case. |
| Memory corruption in Automotive Multimedia due to improper access control in HAB. |
| Information disclosure due to buffer over read in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile |
| Memory corruption due to untrusted pointer dereference in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile |
| Memory corruption due to double free issue in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile |
| Memory corruption in automotive multimedia due to use of out-of-range pointer offset while parsing command request packet with a very large type value. in Snapdragon Auto |
| Memory corruption may occur during IO configuration processing when the IO port count is invalid. |
| Possible memory corruption in kernel while performing memory access due to hypervisor not correctly invalidated the processor translation caches in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile |
| Memory corruption due to stack-based buffer overflow in Core |
