Use After Free in DSP Services
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 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 during PlayReady APP usecase while processing TA commands.
Memory corruption while processing a malformed license file during reboot.
Memory corruption while performing encryption and decryption commands.
Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input.
Memory Corruption in Audio while invoking IOCTLs calls from the user-space.