| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption during the secure boot process, when the `bootm` command is used, it bypasses the authentication of the kernel/rootfs image. |
| Information disclosure while parsing sub-IE length during new IE generation. |
| Transient DOS while loading the TA ELF file. |
| Memory corruption while performing finish HMAC operation when context is freed by keymaster. |
| Information disclosure while handling SA query action frame. |
| INformation disclosure while handling Multi-link IE in beacon frame. |
| Transient DOS in WLAN Firmware while processing a FTMR frame. |
| Memory corruption while sending an Assoc Request having BTM Query or BTM Response containing MBO IE. |
| Transient DOS while converting TWT (Target Wake Time) frame parameters in the OTA broadcast. |
| Transient DOS in WLAN Firmware while parsing WLAN beacon or probe-response frame. |
| Transient DOS in WLAN Firmware when firmware receives beacon including T2LM IE. |
| Transient DOS in WLAN Firmware while parsing t2lm buffers. |
| Memory corruption in WLAN Firmware while parsing a NAN management frame carrying a S3 attribute. |
| Under certain scenarios the WLAN Firmware will reach an assertion due to state confusion while looking up peer ids. |
| 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. |
| 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. |
