Memory corruption while retrieving the CBOR data from TA

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

memory corruption while processing IOCTL commands, when the buffer in write loopback mode is accessed after being freed

Memory corruption while processing escape code, when DisplayId is passed with large unsigned value

Memory corruption while processing image encoding, when configuration is NULL in IOCTL parameter

Memory corruption while processing image encoding, when input buffer length is 0 in IOCTL call

Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer

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 when IOCTL call is invoked from user-space to write board data to WLAN driver

Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver

Memory corruption may occur while reading board data via IOCTL call when the WLAN driver copies the content to the provided output buffer

Memory corruption while IOCTL call is invoked from user-space to read board data

Memory corruption occurs when handling client calls to EnableTestMode through an Escape call

Memory corruption while processing escape code in API

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

Memory corruption may occour while generating test pattern due to negative indexing of display ID

Memory corruption while configuring a Hypervisor based input virtual device

Stack-based Buffer Overflow in WLAN Windows Host

Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in WLAN Windows Host

Memory corruption while invoking IOCTL calls from user space to issue factory test command inside WLAN driver

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

Memory corruption while IOCLT is called when device is in invalid state and the WMI command buffer may be freed twice

Memory corruption while station LL statistic handling

Memory corruption while taking snapshot when an offset variable is set by camera driver

Use After Free in DSP Services

Use After Free in DSP Service

Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Computer Vision

Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in FM Host

Buffer Over-read in Display

Return of Stack Variable Address in Buses

Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in FM Host

Untrusted Pointer Dereference in Computer Vision

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 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 processing IOCTL handler in FastRPC

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

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