| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper. |
| Transient DOS while processing TIM IE from beacon frame as there is no check for IE length. |
| Transient DOS may occur while processing the country IE. |
| Memory Corruption in WLAN HOST while processing WLAN FW request to allocate memory. |
| Transient DOS during hypervisor virtual I/O operation in a virtual machine. |
| Memory Corruption in WLAN HOST while parsing QMI WLAN Firmware response message. |
| Memory Corruption in Data Modem while processing DMA buffer release event about CFR data. |
| Arbitrary memory overwrite when VM gets compromised in TX write leading to Memory Corruption. |
| Memory Corruption in Modem due to double free while parsing the PKCS15 sim files. |
| Weak Configuration due to improper input validation in Modem while processing LTE security mode command message received from network. |
| Memory corruption in WLAN HAL while handling command through WMI interfaces. |
| Memory corruption in WLAN Firmware while parsing receieved GTK Keys in GTK KDE. |
| Memory corruption in Linux when the file upload API is called with parameters having large buffer. |
| Memory corruption in Graphics while processing user packets for command submission. |
| 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. |
| 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. |
