| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption when multiple threads try to unregister the CVP buffer at the same time. |
| Memory corruption while Configuring the SMR/S2CR register in Bypass mode. |
| Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer access. |
| Information disclosure as NPU firmware can send invalid IPC message to NPU driver as the driver doesn`t validate the IPC message received from the firmware. |
| Memory corruption while parsing sensor packets in camera driver, user-space variable is used while allocating memory in kernel and parsing which can lead to huge allocation or invalid memory access. |
| Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released. |
| Memory corruption when allocating and accessing an entry in an SMEM partition. |
| Memory corruption when an invoke call and a TEE call are bound for the same trusted application. |
| Memory corruption while processing key blob passed by the user. |
| Transient DOS while loading the TA ELF file. |
| Memory corruption while performing finish HMAC operation when context is freed by keymaster. |
| Transient DOS while converting TWT (Target Wake Time) frame parameters in the OTA broadcast. |
| Memory corruption while receiving a message in Bus Socket Transport Server. |
| Permanent DOS in Hypervisor while untrusted VM without PSCI support makes a PSCI call. |
| Memory corruption in Graphics while processing user packets for command submission. |
| Transient DOS in WLAN Firmware while interpreting MBSSID IE of a received beacon frame. |
| In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used. So when a function called cam_mem_get_cpu_buf to get the kernel va to use, another thread can call CAM_REQ_MGR_RELEASE_BUF to unmap the kernel va which cause UAF of the kernel address. |
| The buffer obtained from kernel APIs such as cam_mem_get_cpu_buf() may be readable/writable in userspace after kernel accesses it. In other words, user mode may race and modify the packet header (e.g. header.count), causing checks (e.g. size checks) in kernel code to be invalid. This may lead to out-of-bounds read/write issues. |
| The cam_get_device_priv function does not check the type of handle being returned (device/session/link). This would lead to invalid type usage if a wrong handle is passed to it. |
| Memory corruption in WLAN HAL while parsing WMI command parameters. |
