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.

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

Memory corruption while processing frame command IOCTL calls.

Memory corruption while invoking IOCTL calls to unmap the DMA buffers.

Memory corruption when input parameter validation for number of fences is missing for fence frame IOCTL calls,