Reusing a Nonce, Key Pair in Encryption in HLOS
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed.
Memory corruption when the mapped pages in VBO are still mapped after reclaiming by shrinker.
Memory corruption while processing IOCTL command when multiple threads are called to map/unmap buffer concurrently.
Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations.
Memory corruption when processing draw objects of incorrect type during graphics command list execution.
Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms.
Memory Corruption when processing camera CRE driver operations with improper handling of buffer limits during hardware update preparation.
Memory corruption when processing command buffer requests with invalid length parameters in the Android Camera driver.
Memory corruption when processing camera requests with excessive batch and IO buffer configurations exceeds allocated memory size.
Transient DOS when processing authentication frames with invalid FILS information element header lengths.
Memory Corruption when processing I2C transfer requests due to a race condition between memory allocation and data copying.
Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration.
Memory Corruption when handling malformed request parameters in the fingerprint TA.
Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values.
Memory corruption while processing a packet with a size close to the maximum allowed value.
Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification.
Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits.
Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks.
Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.