Qualcomm

Memory corruption while IOCTL call is invoked from user-space to read board data.

Memory corruption while processing memory map or unmap IOCTL operations simultaneously.

Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads.

Memory corruption occurs when handling client calls to EnableTestMode through an Escape call.

Memory corruption while processing escape code in API.

Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation.

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

Memory corruption while handling file descriptor during listener registration/de-registration.

Memory corruption while processing IOCTL calls.

Memory corruption while calling the NPU driver APIs concurrently.

Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset.

Memory corruption while doing Escape call when user provides valid kernel address in the place of valid user buffer address.

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 in display driver while detaching a device.

Memory corruption may occur while accessing a variable during extended back to back tests.

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

Memory corruption may occur while validating ports and channels in Audio driver.

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

Information disclosure may occur due to improper permission and access controls to Video Analytics engine.

Memory corruption may occur during the synchronization of the camera`s frame processing pipeline.

Memory corruption while handling multuple IOCTL calls from userspace for remote invocation.

Memory corruption caused by missing locks and checks on the DMA fence and improper synchronization.

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 processing command in Glink linux.

Memory corruption while processing camera use case IOCTL call.

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

Memory corruption while Invoking IOCTL calls from user-space to validate FIPS encryption or decryption functionality.

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 in Camera due to unusually high number of nodes passed to AXI port.

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

Memory corruption while validating number of devices in Camera kernel .

Memory corruption may occour while generating test pattern due to negative indexing of display ID.

Memory corruption may occour occur when stopping the WLAN interface after processing a WMI command from the interface.

Memory corruption while handling IOCTL call from user-space to set latency level.

Memory corruption while taking a snapshot with hardware encoder due to unvalidated userspace buffer.

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

Memory corruption can occur when process-specific maps are added to the global list. If a map is removed from the global list while another thread is using it for a process-specific task, issues may arise.

Memory corruption occurs when invoking any IOCTL-calling application that executes all MCDM driver IOCTL calls.

Memory corruption while processing FIPS encryption or decryption validation functionality IOCTL call.

Memory corruption while processing IOCTL call invoked from user-space to verify non extension FIPS encryption and decryption functionality.

Memory corruption while processing FIPS encryption or decryption IOCTL call invoked from user-space.

Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.