Integer Overflow or Wraparound in Graphics Linux

Use After Free in Graphics

Memory corruption in Bluetooth HOST due to buffer overflow while parsing the command response received from remote

Possible integer overflow due to improper check of batch count value while sanitizer is enabled in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon…

Information disclosure when an invalid RTCP packet is received during a VoLTE/VoWiFi IMS call

Information disclosure may occur while decoding the RTP packet with invalid header extension from network

Information disclosure may occur during a video call if a device resets due to a non-conforming RTCP packet that doesn`t adhere to RFC standards

Missing Authorization in Core

Out-of-bounds Write in HLOS

Buffer Copy Without Checking Size of Input in Automotive Audio

Use After Free in Automotive Audio

Use After Free in Automotive Audio

Use After Free in Automotive Audio

Improper Release of Memory Before Removing Last Reference in Graphics

Use After Free in Automotive Linux OS

Buffer Copy Without Checking Size of Input in Core Services

Use After Free in Video

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

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

Memory corruption while processing GPU commands

Memory corruption when a compat IOCTL call is followed by another IOCTL call from userspace to a 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 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 while processing key blob passed by the user

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

Memory corruption while invoking IOCTLs calls in Automotive Multimedia

Memory corruption while invoking HGSL IOCTL context create

Memory corruption while running NPU, when NETWORK_UNLOAD and (NETWORK_UNLOAD or NETWORK_EXECUTE_V2) commands are submitted at the same time

Memory corruption while receiving a message in Bus Socket Transport Server

Memory corruption in TZ Secure OS while requesting a memory allocation from TA region

Memory corruption in HLOS while invoking IOCTL calls from user-space

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