Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling.
Memory corruption caused by missing locks and checks on the DMA fence and improper synchronization.
Memory corruption during concurrent buffer access due to modification of the reference count.
Memory corruption when kernel driver attempts to trigger hardware fences.
Memory corruption while handling concurrent memory mapping and unmapping requests from a user-space application.
Memory corruption while accessing a synchronization object during concurrent operations.
Memory corruption while processing IOCTL calls to unmap the buffers.
Memory corruption while processing graphics kernel driver request to create DMA fence.
Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.
Memory corruption when input parameter validation for number of fences is missing for fence frame IOCTL calls,
Memory Corruption when accessing a buffer after it has been freed while processing IOCTL calls.
Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocation of buffer resources.
Memory Corruption when user space address is modified and passed to mem_free API, causing kernel memory to be freed inadvertently.
Memory corruption while passing untrusted/corrupted pointers from DSP to EVA.
Memory corruption during concurrent SSR execution due to race condition on the global maps list.
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 while processing user packets to generate page faults.
Memory corruption while maintaining memory maps of HLOS memory.
Memory Corruption when multiple threads concurrently access and modify shared resources.
Page 1+ Next →