| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| 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. |
| 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 non-secure loader rewrites page tables before secure memory initialization. |
| Memory corruption while processing IOCTL command called from user space to the kernel with invalid parameters. |
| 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. |
| Information Disclosure when processing wireless network channel switch information with improperly formatted length fields. |
| Cryptographic Issue while processing registration requests with malformed or missing authentication parameters. |
| 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. |
| Information Disclosure when IPSec negotiation fails or is not established properly during NG-eCall SIP signaling. |
| Memory Corruption while processing IOCTL device driver requests with invalid arguments. |
| Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities. |
| 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. |
| Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security. |
| Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer. |
| Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization. |
