| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption when dynamically changing the size of a previously allocated buffer while its contents are being modified. |
| Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level. |
| Memory Corruption when copying data from a freed source while executing performance counter deselect operation. |
| Memory corruption may occur while accessing a variable during extended back to back tests. |
| 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 reading secure file. |
| Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur. |
| Memory corruption while reading the FW response from the shared queue. |
| Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses. |
| Memory corruption while retrieving the CBOR data from TA. |
| Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input. |
| Memory Corruption when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors. |
| Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers. |
| Information disclosure while decoding this RTP packet Payload when UE receives the RTP packet from the network. |
| Transient DOS may occur while processing malformed length field in SSID IEs. |
| Memory corruption while processing video packets received from video firmware. |
| Transient DOS while processing IKEv2 Informational request messages, when a malformed fragment packet is received. |
| Memory corruption when there is failed unmap operation in GPU. |
| Memory corruption when the payload received from firmware is not as per the expected protocol size. |
| Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmware. |
