Use After Free in Automotive Android OS
Memory corruption may occur while accessing a variable during extended back to back tests.
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 parsing the ML IE due to invalid frame content.
Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling.
Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.
Memory corruption while triggering commands in the PlayReady Trusted application.
Memory corruption during the FRS UDS generation process.
Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur.
Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation.
Memory corruption while processing multiple IOCTL calls from HLOS to DSP.
Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses.
Memory corruption while performing private key encryption in trusted application.
memory corruption while loading a PIL authenticated VM, when authenticated VM image is loaded without maintaining cache coherency.
Memory corruption while selecting the PLMN from SOR failed list.
Memory corruption due to global buffer overflow when a test command uses an invalid payload type.
Memory corruption during PlayReady APP usecase while processing TA commands.
Memory corruption while processing a malformed license file during reboot.