Memory corruption may occur while attaching VM when the HLOS retains access to VM

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 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 while reading the FW response from the shared queue

Memory corruption during the FRS UDS generation process

Memory corruption while triggering commands in the PlayReady Trusted application

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

Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling

Memory corruption while reading secure file

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 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 handling file descriptor during listener registration/de-registration

Memory corruption while calling the NPU driver APIs concurrently

Memory corruption in display driver while detaching a device

Memory corruption may occur while validating ports and channels in Audio driver

Memory corruption while processing IOCTL from user space to handle GPU AHB bus error

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

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

Memory corruption while handling IOCTL call from user-space to set latency level

Memory corruption while configuring a Hypervisor based input virtual device

Use After Free in DSP Services

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 when invalid input is passed to invoke GPU Headroom API call

Memory corruption when allocating and accessing an entry in an SMEM partition continuously

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

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 FM Host

Return of Stack Variable Address in Buses

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

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 can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table

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 while processing graphics kernel driver request to create DMA fence

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 allocating and accessing an entry in an SMEM partition

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