Memory Corruption when multiple threads simultaneously access a memory free API.
Memory Corruption when multiple threads concurrently access and modify shared resources.
Memory corruption due to double free when multiple threads race to set the timestamp store.
Memory corruption during concurrent buffer access due to modification of the reference count.
Memory corruption while accessing a synchronization object during concurrent operations.
Memory corruption while handling concurrent memory mapping and unmapping requests from a user-space application.
Memory corruption caused by missing locks and checks on the DMA fence and improper synchronization.
Memory corruption while unmapping the fastrpc map when two threads can free the same map in concurrent scenario.
Memory corruption during sub-system restart while processing clean-up to free up resources.
Memory corruption when two threads try to map and unmap a single node simultaneously.
Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.
Memory corruption may occur while accessing a variable during extended back to back tests.
Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling.
Memory corruption while releasing shared resources in MinkSocket listener thread.
Memory corruption while processing user packets to generate page faults.
Memory corruption while processing IOCTL command when multiple threads are called to map/unmap buffer concurrently.
Memory Corruption when user space address is modified and passed to mem_free API, causing kernel memory to be freed inadvertently.
Memory corruption while processing GPU commands.
Memory corruption while processing event close when client process terminates abruptly.
Memory corruption while processing memory map or unmap IOCTL operations simultaneously.
Page 1+ Next →