| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size. |
| 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. |
| Information disclosure while parsing sub-IE length during new IE generation. |
| 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. |
| Memory corruption while sending an Assoc Request having BTM Query or BTM Response containing MBO IE. |
| Under certain scenarios the WLAN Firmware will reach an assertion due to state confusion while looking up peer ids. |
| 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 while sending SMS from AP firmware. |
| Memory corruption in Graphics while processing user packets for command submission. |
| Transient DOS in WLAN Host when an invalid channel (like channel out of range) is received in STA during CSA IE. |
| Transient DOS in WLAN Host while doing channel switch announcement (CSA), when a mobile station receives invalid channel in CSA IE. |
| Transient DOS in WLAN Firmware while interpreting MBSSID IE of a received beacon frame. |
| Transient DOS in WLAN Host when a mobile station receives invalid channel in CSA IE while doing channel switch announcement (CSA). |
| 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. |
