Memory corruption may occur during IO configuration processing when the IO port count is invalid.
Memory corruption while calling the NPU driver APIs concurrently.
Memory corruption while processing command in Glink linux.
Information disclosure while deriving keys for a session for any Widevine use case.
Transient DOS may occur while processing the country IE.
Memory corruption may occur while validating ports and channels in Audio driver.
Memory corruption while parsing the memory map info in IOCTL calls.
Information disclosure during audio playback.
Memory corruption when multiple threads try to unregister the CVP buffer at the same time.
Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer access.
Information disclosure as NPU firmware can send invalid IPC message to NPU driver as the driver doesnt validate the IPC message received from the firmware.
Memory corruption while parsing sensor packets in camera driver, user-space variable is used while allocating memory in kernel and parsing which can lead to huge allocation or invalid memory access.
Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.
Transient DOS while processing TIM IE from beacon frame as there is no check for IE length.
Memory corruption when Alternative Frequency offset value is set to 255.
Transient DOS during music playback of ALAC content.
Memory corruption while receiving a message in Bus Socket Transport Server.
Memory Corruption in Radio Interface Layer while sending an SMS or writing an SMS to SIM.
Memory corruption in WLAN HAL while handling command through WMI interfaces.
Memory corruption in RIL due to Integer Overflow while triggering qcriluimrequestapdu request.
Memory Corruption due to improper validation of array index in Linux while updating adn record.
Memory corruption due to buffer over-read in Modem while processing SetNativeHandle RTP service.
Memory corruption in WLAN HAL while parsing WMI command parameters.
Memory corruption in WLAN Firmware while parsing receieved GTK Keys in GTK KDE.
Transient DOS in WLAN Firmware while interpreting MBSSID IE of a received beacon frame.
Memory corruption in Graphics while processing user packets for command submission.
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 GPS HLOS Driver when injectFdclData receives data with invalid data length.