Memory Corruption when user space address is modified and passed to mem_free API, causing kernel memory to be freed inadvertently.
Memory corruption while handling concurrent memory mapping and unmapping requests from a user-space application.
Memory corruption when dereferencing an invalid userspace address in a user buffer during MCDM IOCTL processing.
Memory corruption while registering a buffer from user-space to kernel-space using IOCTL calls.
Memory corruption while processing a config call from userspace.
Memory corruption can occur during context user dumps due to inadequate checks on buffer length.
Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.
Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling.
Memory corruption while processing user buffers.
Memory corruption while processing user packets to generate page faults.
Memory corruption when blob structure is modified by user-space after kernel verification.
Memory Corruption when multiple threads simultaneously access a memory free API.
Memory corruption may occur while accessing a variable during extended back to back tests.
Memory corruption during sub-system restart while processing clean-up to free up resources.
Memory corruption during concurrent buffer access due to modification of the reference count.
Memory corruption caused by missing locks and checks on the DMA fence and improper synchronization.
Memory corruption while invoking IOCTL calls from user-space to kernel-space to handle session errors.
Memory corruption while sending the persist buffer command packet from the user-space to the kernel space through the IOCTL call.
Memory corruption while submitting blob data to kernel space though IOCTL.
Memory corruption while handling multiple IOCTL calls from userspace to operate DMA operations.
Page 1+ Next →