| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption during management frame processing due to mismatch in T2LM info element. |
| Memory corruption when AP includes TID to link mapping IE in the beacons and STA is parsing the beacon TID to link mapping IE. |
| Memory corruption when IOMMU unmap of a GPU buffer fails in Linux. |
| Information disclosure in Audio while accessing AVCS services from ADSP payload. |
| Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses. |
| Memory corruption in video while parsing the Videoinfo, when the size of atom is greater than the videoinfo size. |
| Memory corruption while retrieving the CBOR data from TA. |
| Transient DOS in Audio when invoking callback function of ASM driver. |
| Memory corruption while processing MBSSID beacon containing several subelement IE. |
| Memory corruption can occur when process-specific maps are added to the global list. If a map is removed from the global list while another thread is using it for a process-specific task, issues may arise. |
| Memory corruption while processing the event ring, the context read pointer is untrusted to HLOS and when it is passed with arbitrary values, may point to address in the middle of ring element. |
| Transient DOS can occur when the driver parses the per STA profile IE and tries to access the EXTN element ID without checking the IE length. |
| Memory corruption while processing finish_sign command to pass a rsp buffer. |
| Memory corruption when the payload received from firmware is not as per the expected protocol size. |
| Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame. |
| Memory corruption in Core Services while executing the command for removing a single event listener. |
| Memory corruption when BTFM client sends new messages over Slimbus to ADSP. |
| Transient DOS while processing TIM IE from beacon frame as there is no check for IE length. |
| Memory corruption when preparing a shared memory notification for a memparcel in Resource Manager. |
| Memory corruption may occur while accessing a variable during extended back to back tests. |
