Out-of-bounds Write in Computer Vision

Out-of-bounds Write in Computer Vision

Improper Input Validation in Automotive Software platform based on QNX

Improper Input Validation in HLOS

Improper Access Control in Hypervisor

Out-of-bounds Write in Audio

Use After Free in HLOS

Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in Automotive Vehicle Networks

Use After Free in Automotive Linux OS

Use After Free in HLOS

Improper Input Validation in Automotive OS Platform

NULL Pointer Dereference in Display

Use After Free in Automotive Android OS

Untrusted Pointer Dereference in Automotive Android OS

Use After Free in WLAN Host Communication

Improper Input Validation in Hypervisor

Integer Overflow to Buffer Overflow in Automotive OS Platform

Use After Free in DSP Services

Improper Validation of Array Index in Hypervisor

Use After Free in DSP Services

Use After Free in Qualcomm IPC

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 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 when more scan frequency list or channels are sent from the user space

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