Incorrect Authorization in Graphics

Incorrect Authorization in Graphics Windows

Integer Overflow or Wraparound in Graphics Linux

Use of Out-of-range Pointer Offset in Graphics

Memory corruption in Hypervisor when platform information mentioned is not aligned

Integer Overflow or Wraparound in Display

Buffer Over-read in Data Network Stack & Connectivity

Information disclosure may occur while decoding the RTP packet with improper header length for number of contributing sources

Buffer Over-read in Multi Mode Call Processor

Missing Authorization in Core

Out-of-bounds Write in HLOS

Stack-based Buffer Overflow in Camera Driver

Use After Free in Graphics

Improper Release of Memory Before Removing Last Reference in Graphics

Integer Overflow or Wraparound in Audio

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 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 can occur when TME processes addresses from TZ and MPSS requests without proper validation

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

Use After Free in DSP Services

Buffer Copy Without Checking Size of Input in Data Network Stack & Connectivity

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

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 while creating a fence to wait on timeline events, and simultaneously signal timeline events

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 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 copying a keyblob`s material when the key material`s size is not accurately checked

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 while processing a QMI request for allocating memory from a DHMS supported subsystem

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

Memory corruption when resource manager sends the host kernel a reply message with multiple fragments

Memory corruption while receiving a message in Bus Socket Transport Server

Memory corruption while processing pin reply in Bluetooth, when pin code received from APP layer is greater than expected size

Memory corruption in Core while processing RX intent request

Memory corruption in BT controller while parsing debug commands with specific sub-opcodes at HCI interface level