Memory corruption when another driver calls an IOCTL with invalid input/output buffer.
Memory corruption while accessing a buffer during IOCTL processing.
Memory corruption when IOCTL interface is called to map and unmap buffers simultaneously.
Memory corruption while processing IOCTL calls to unmap the buffers.
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing.
Memory corruption when a compat IOCTL call is followed by another IOCTL call from userspace to a driver.
Memory corruption while IOCTL call is invoked from user-space to read board data.
Memory corruption while invoking IOCTL calls to unmap the DMA buffers.
Memory corruption while processing IOCTL calls.
Memory corruption occurs when invoking any IOCTL-calling application that executes all MCDM driver IOCTL calls.
Memory corruption while IOCLT is called when device is in invalid state and the WMI command buffer may be freed twice.
Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.
Memory corruption while processing frame command IOCTL calls.
Memory corruption while processing an IOCTL request, when buffer significantly exceeds the command argument limit.
Memory corruption may occur while reading board data via IOCTL call when the WLAN driver copies the content to the provided output buffer.
Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace.
Memory corruption while invoking IOCTL map buffer request from userspace.
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 write board data to WLAN driver.
Memory corruption while registering a buffer from user-space to kernel-space using IOCTL calls.
Page 1+ Next →