| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security. |
| Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed. |
| Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations. |
| Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration. |
| Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization. |
| Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. |
| Memory Corruption when processing device identifier strings that exceed the expected maximum length. |
| Memory Corruption when processing display command line information due to improper initialization of a variable. |
| Memory corruption while processing fastboot OEM commands. |
| Memory corruption while processing fastboot commands with invalid input. |
| Cryptographic issue while processing partition table entries allows unauthorized modification of boot flow. |
| Memory corruption while processing fastboot commands with improperly formatted input. |
| Memory Corruption when processing fastboot commands to set display mode. |
| Memory Corruption when copying data from a freed source while executing performance counter deselect operation. |
| Memory Corruption when accessing buffers with invalid length during TA invocation. |
| Memory corruption may occur while accessing a variable during extended back to back tests. |
| Memory corruption while calling the NPU driver APIs concurrently. |
| 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 during memory assignment to headless peripheral VM due to incorrect error code handling. |
