Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmware.
Transient DOS when importing a PKCS#8-encoded RSA private key with a zero-sized modulus.
Memory corruption while retrieving the CBOR data from TA.
Memory corruption while processing video packets received from video firmware.
Memory corruption while processing manipulated payload in video firmware.
Information disclosure while processing the hash segment in an MBN file.
Information disclosure while reading data from an image using specified offset and size parameters.
memory corruption while loading a PIL authenticated VM, when authenticated VM image is loaded without maintaining cache coherency.
Memory corruption while performing private key encryption in trusted application.
Memory corruption while processing a malformed license file during reboot.
Memory corruption during PlayReady APP usecase while processing TA commands.
Memory corruption while performing encryption and decryption commands.
Information disclosure while exposing internal TA-to-TA communication APIs to HLOS
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.
Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.
Memory corruption during the FRS UDS generation process.
Memory corruption while triggering commands in the PlayReady Trusted application.
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.
Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input.
Memory Corruption in SPS Application while exporting public key in sorter TA.
Memory corruption while loading an ELF segment in TEE Kernel.
Cryptographic issues while generating an asymmetric key pair for RKP use cases.
Information disclosure while creating MQ channels.
Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification failure, potentially leading to a user throttling bypass.