| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| 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. |
| Memory corruption while using the UIM diag command to get the operators name. |
| Memory corruption in Boot while running a ListVars test in UEFI Menu during boot. |
| Transient DOS in WLAN firmware while parsing MLO (multi-link operation). |
| Transient DOS in WLAN Firmware while interpreting MBSSID IE of a received beacon frame. |
| Information disclosure in Core services while processing a Diag command. |
| Transient DOS in Bluetooth Host while rfc slot allocation. |
| Memory corruption in BT controller while parsing debug commands with specific sub-opcodes at HCI interface level. |
| Memory corruption while loading an ELF segment in TEE Kernel. |
| Transient DOS in WLAN Host when a mobile station receives invalid channel in CSA IE while doing channel switch announcement (CSA). |
| Memory corruption when IPv6 prefix timer object`s lifetime expires which are created while Netmgr daemon gets an IPv6 address. |
| Memory corruption in WLAN Firmware while parsing receieved GTK Keys in GTK KDE. |
| Memory corruption in WLAN Host while setting the PMK length in PMK length in internal cache. |
| Memory Corruption in WLAN Host while deserializing the input PMK bytes without checking the input PMK length. |
| 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 core services when Diag handler receives a command to configure event listeners. |
