Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses

Memory corruption during the FRS UDS generation process

Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions

Memory corruption while processing memory map or unmap IOCTL operations simultaneously

Memory corruption while processing input message passed from FE driver

Memory corruption may occur while accessing a variable during extended back to back tests

Memory corruption while power-up or power-down sequence of the camera sensor

Memory corruption can occur in the camera when an invalid CID is used

Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace

Memory corruption may occour occur when stopping the WLAN interface after processing a WMI command from the interface

Memory corruption while configuring a Hypervisor based input virtual device

Use After Free in DSP Services

Memory corruption while Configuring the SMR/S2CR register in Bypass mode

Memory corruption while processing GPU commands

Memory corruption while processing user packets to generate page faults

Use After Free in DSP Services

Use After Free in DSP Service

Return of Stack Variable Address in Buses

Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time

Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released

Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events

Memory corruption while allocating memory in HGSL driver

Memory corruption while processing IOCTL call to set metainfo

Memory corruption when kernel driver attempts to trigger hardware fences

Memory corruption while processing graphics kernel driver request to create DMA fence

Memory corruption when memory mapped in a VBO is not unmapped by the GPU SMMU

Memory corruption while handling user packets during VBO bind operation

Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released

Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size

Memory corruption when an invoke call and a TEE call are bound for the same trusted application

Memory corruption while processing key blob passed by the user

Memory corruption while performing finish HMAC operation when context is freed by keymaster

Memory corruption while copying a keyblob`s material when the key material`s size is not accurately checked

Memory corruption in TZ Secure OS while Tunnel Invoke Manager initialization

Memory corruption when the IOCTL call is interrupted by a signal

Memory corruption as GPU registers beyond the last protected range can be accessed through LPAC submissions

Memory corruption when the payload received from firmware is not as per the expected protocol size

Memory corruption when IOMMU unmap of a GPU buffer fails in Linux

Memory corruption while verifying the serialized header when the key pairs are generated

Memory corruption in HLOS while checking for the storage type

Memory corruption in Kernel while handling GPU operations

Memory corruption while processing buffer initialization, when trusted report for certain report types are generated

Memory corruption while processing finish_sign command to pass a rsp buffer

Memory corruption in SPS Application while requesting for public key in sorter TA

Memory corruption while processing a QMI request for allocating memory from a DHMS supported subsystem

Memory corruption while processing TPC target power table in FTM TPC

Memory corruption while invoking IOCTLs calls in Automotive Multimedia

Memory corruption while invoking HGSL IOCTL context create

Memory corruption while processing the event ring, the context read pointer is untrusted to HLOS and when it is passed with arbitrary values, may point to address in the middle of…

Memory corruption in Core when updating rollback version for TA and OTA feature is enabled