Memory corruption in WLAN Firmware while parsing receieved GTK Keys in GTK KDE.
Memory corruption in Graphics while processing user packets for command submission.
Transient DOS in WLAN Firmware while interpreting MBSSID IE of a received beacon frame.
In the function call related to CAMREQMGRRELEASEBUF there is no check if the buffer is being used. So when a function called cammemgetcpubuf to get the kernel va to use, another thread can call CAMREQMGRRELEASEBUF to unmap the kernel va which cause UAF of the kernel address.
The buffer obtained from kernel APIs such as cammemgetcpubuf() may be readable/writable in userspace after kernel accesses it. In other words, user mode may race and modify the packet header (e.g. header.count), causing checks (e.g. size checks) in kernel code to be invalid. This may lead to out-of-bounds read/write issues.
The camgetdevicepriv function does not check the type of handle being returned (device/session/link). This would lead to invalid type usage if a wrong handle is passed to it.
Memory Corruption in WLAN HOST while fetching TX status information.
Memory Corruption in Audio while allocating the ion buffer during the music playback.
Arbitrary memory overwrite when VM gets compromised in TX write leading to Memory Corruption.
Memory corruption in Video while calling APIs with different instance ID than the one received in initialization.
Memory corruption in Linux while calling system configuration APIs.
Memory Corruption in Data Network Stack & Connectivity when sim gets detected on telephony.
Memory Corruption in Linux while processing QcRilRequestImsRegisterMultiIdentityMessage request.
Weak Configuration due to improper input validation in Modem while processing LTE security mode command message received from network.
Memory Corruption in Modem due to double free while parsing the PKCS15 sim files.
Information disclosure in DSP Services while loading dynamic module.