| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Information disclosure while running video usecase having rogue firmware. |
| Information disclosure when Video engine escape input data is less than expected minimum size. |
| Memory corruption while processing config_dev IOCTL when camera kernel driver drops its reference to CPU buffers. |
| Memory corruption while processing message in guest VM. |
| Memory corruption while processing data sent by FE driver. |
| Memory corruption while handling repeated memory unmap requests from guest VM. |
| Memory corruption due to double free when multiple threads race to set the timestamp store. |
| Memory corruption due to global buffer overflow when a test command uses an invalid payload type. |
| Cryptographic issue while performing RSA PKCS padding decoding. |
| Memory corruption when the UE receives an RTP packet from the network, during the reassembly of NALUs. |
| Information disclosure when UE receives the RTP packet from the network, while decoding and reassembling the fragments from RTP packet. |
| Information disclosure while decoding RTP packet received by UE from the network, when payload length mentioned is greater than the available buffer length. |
| Information disclosure while decoding this RTP packet headers received by UE from the network when the padding bit is set. |
| memory corruption while loading a PIL authenticated VM, when authenticated VM image is loaded without maintaining cache coherency. |
| Transient DOS while parsing the EPTM test control message to get the test pattern. |
| Memory corruption while selecting the PLMN from SOR failed list. |
| Integer overflow in the fb_mmap function in drivers/video/fbmem.c in the Linux kernel before 3.8.9, as used in a certain Motorola build of Android 4.1.2 and other products, allows local users to create a read-write memory mapping for the entirety of kernel memory, and consequently gain privileges, via crafted /dev/graphics/fb0 mmap2 system calls, as demonstrated by the Motochopper pwn program. |
| Memory corruption may occur while processing device IO control call for session control. |
| Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads. |
| Memory corruption while processing memory map or unmap IOCTL operations simultaneously. |
