Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number
Memory Corruption when processing auxiliary sensor input/output control commands with insufficient buffer size validation.
Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur.
Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling.
In an out-of-memory scenario an allocation could fail but free would have been called on the pointer afterwards leading to memory corruption. This vulnerability affects Firefox < 128, Firefox ESR < 11
Memory corruption when copying overlapping buffers during memory operations due to incorrect offset calculations.
There is a memory corruption vulnerability due to an out-of-bounds write when loading a corrupted DSB file in Digilent DASYLab. This vulnerability may result in information disclosure or arbitrary co
A flaw was found in the GNU Binutils BFD library, a widely used component for handling binary files such as object files and executables. The issue occurs when processing specially crafted XCOFF objec
Memory corruption while processing IOCTL command when multiple threads are called to map/unmap buffer concurrently.
CWE-415: Double Free vulnerability exists that could cause heap memory corruption when the end user imports a malicious project file (SSD file) shared by the attacker into Rapsody.
Memory corruption while processing fastboot commands with improperly formatted input.
Memory corruption while accessing a synchronization object during concurrent operations.
Memory corruption while handling file descriptor during listener registration/de-registration.
Memory corruption can occur when process-specific maps are added to the global list. If a map is removed from the global list while another thread is using it for a process-specific task, issues may a
Memory corruption when two threads try to map and unmap a single node simultaneously.
Memory corruption while processing fastboot commands with invalid input.
There is a memory corruption vulnerability due to an out-of-bounds read when loading a corrupted file in Digilent DASYLab. This vulnerability may result in information disclosure or arbitrary code ex
There is a memory corruption vulnerability due to an out-of-bounds read when loading a corrupted file in Digilent DASYLab. This vulnerability may result in information disclosure or arbitrary code ex