Memory corruption may occur during IO configuration processing when the IO port count is invalid.
Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory.
Memory corruption while processing concurrent IOCTL calls.
Memory corruption while processing IOCTL command when multiple threads are called to map/unmap buffer concurrently.
Memory corruption while IOCTL call is invoked from user-space to read board data.
Memory corruption while parsing the memory map info in IOCTL calls.
Memory corruption may occur while processing IOCTL call for DMM/WARPNCC CONFIG request.
Memory corruption when another driver calls an IOCTL with invalid input/output buffer.
Memory corruption while processing IOCTL calls.
Memory corruption may occur while processing message from frontend during allocation.
Memory corruption occurs when a secure application is launched on a device with insufficient memory.
Memory corruption while processing an IOCTL request, when buffer significantly exceeds the command argument limit.
Memory corruption while processing IOCTL calls to add route entry in the HW.
Memory corruption while handling invalid inputs in application info setup.
Memory corruption while processing a frame request from user.
Memory corruption while accessing MSM channel map and mixer functions.
Memory corruption during dynamic process creation call when client is only passing address and length of shell binary.
Memory corruption while processing DDI call with invalid buffer.
Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace.
Memory corruption may occur while processing the OIS packet parser.
Page 1+ Next →