Integer Overflow or Wraparound in Automotive GPU
Memory corruption while allocating memory in HGSL driver.
Memory corruption while allocating memory in HGSL driver.
Memory corruption while processing IOCTL call to set metainfo.
Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.
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 when the user application modifies the same shared memory asynchronously when kernel is accessing it.
Memory corruption while processing GPU page table switch.
Memory corruption while processing voice packet with arbitrary data received from ADSP.
Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.
Memory corruption while handling session errors from firmware.
Memory corruption when a process invokes IOCTL calls from user-space to create a HAB virtual channel and another process invokes IOCTL calls to destroy the same.
Memory corruption is possible when an attempt is made from userspace or console to write some haptics effects pattern to the haptics debugfs file.
Memory corruption during the network scan request.
Memory corruption while sending the persist buffer command packet from the user-space to the kernel space through the IOCTL call.
Transient DOS when transmission of management frame sent by host is not successful and error status is received in the host.