qualcomm sa9000p firmware vulnerabilities, newest first, page 2

Information disclosure may be there when a guest VM is connected.

Memory corruption may occur due top improper access control in HAB process.

Memory corruption while accessing MSM channel map and mixer functions.

Memory corruption while invoking IOCTL map buffer request from userspace.

Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory.

Memory corruption may occur in keyboard virtual device due to guest VM interaction.

Memory corruption while reading a type value from a buffer controlled by the Guest Virtual Machine.

Memory corruption while processing input message passed from FE driver.

Memory corruption while reading a value from a buffer controlled by the Guest Virtual Machine.

Memory corruption may occur while processing message from frontend during allocation.

Memory corruption may occur during communication between primary and guest VM.

Memory corruption may occur due to improper input validation in clock device.

Memory corruption during voice activation, when sound model parameters are loaded from HLOS, and the received sound model list is empty in HLOS drive.

Memory corruption during voice activation, when sound model parameters are loaded from HLOS to ADSP.

Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.

Memory corruption while reading CPU state data during guest VM suspend.

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.

Memory corruption while parsing the memory map info in IOCTL calls.

Information disclosure while processing IO control commands.

Information disclosure during audio playback.

Information disclosure while processing information on firmware image during core initialization.

Transient DOS can occur when GVM sends a specific message type to the Vdev-FastRPC backend.

Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system imag…

Uncontrolled resource consumption when a driver, an application or a SMMU client tries to access the global registers through SMMU.

information disclosure while invoking the mailbox read API.

Information disclosure while invoking callback function of sound model driver from ADSP for every valid opcode received from sound model driver.

Information Disclosure while invoking the mailbox write API when message received from user is larger than mailbox size.

Memory corruption when multiple threads try to unregister the CVP buffer at the same time.

Memory corruption when PAL client calls PAL service APIs by passing a random value as handle and the handle is not validated by the service.

Information disclosure as NPU firmware can send invalid IPC message to NPU driver as the driver doesn`t validate the IPC message received from the firmware.

Memory corruption while parsing sensor packets in camera driver, user-space variable is used while allocating memory in kernel and parsing which can lead to huge allocation or invalid memory access.

Memory corruption during GNSS HAL process initialization.

Memory corruption while processing GPU commands.

Transient DOS while parsing BTM ML IE when per STA profile is not included.

Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.

Memory corruption while processing user packets to generate page faults.

Transient DOS when transmission of management frame sent by host is not successful and error status is received in the host.

Memory corruption while unmapping the fastrpc map when two threads can free the same map in concurrent scenario.

Memory corruption while invoking IOCTL calls for MSM module from the user space during audio playback and record.

Memory corruption while calculating total metadata size when a very high reserved size is requested by gralloc clients.

Memory corruption while releasing shared resources in MinkSocket listener thread.

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 mapped pages in VBO are still mapped after reclaiming by shrinker.

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 while invoking IOCTL call for GPU memory allocation and size param is greater than expected size.

Information Disclosure while parsing beacon frame in STA.