| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Improper access control for volatile memory containing boot code in Universal Boot Loader (U-Boot) before 2017.11 and Qualcomm chips IPQ4019, IPQ5018, IPQ5322, IPQ6018, IPQ8064, IPQ8074, and IPQ9574 could allow an attacker to execute arbitrary code. |
| Dell Wireless 5932e and Qualcomm Snapdragon X62 Firmware and GNSS/GPS Driver, versions prior to 3.2.0.22 contain an Unquoted Search Path or Element vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Code Execution. |
| Memory corruption while processing a video session to set video parameters. |
| Memory corruption occurs when a secure application is launched on a device with insufficient memory. |
| Transient DOS while parsing video packets received from the video firmware. |
| Memory corruption while deinitializing a HDCP session. |
| Memory corruption while processing identity credential operations in the trusted application. |
| Memory corruption while parsing clock configuration data for a specific hardware type. |
| Cryptographic issue may occur while encrypting license data. |
| Memory corruption while handling buffer mapping operations in the cryptographic driver. |
| Memory corruption while processing a config call from userspace. |
| Transient DOS while parsing a WLAN management frame with a Vendor Specific Information Element. |
| Memory corruption when accessing resources in kernel driver. |
| Memory corruption while performing sensor register read operations. |
| Memory corruption when copying overlapping buffers during memory operations due to incorrect offset calculations. |
| Memory corruption while accessing a synchronization object during concurrent operations. |
| Memory corruption while handling sensor utility operations. |
| Information disclosure while processing a firmware event. |
| Memory corruption while processing shared command buffer packet between camera userspace and kernel. |
| Memory corruption while processing a secure logging command in the trusted application. |