Qualcomm

Memory corruption due to buffer over-read in Modem while processing SetNativeHandle RTP service.

In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used. So when a function called cam_mem_get_cpu_buf to get the kernel va to use, another thread can call CAM_REQ_MGR_RELEASE_BUF to unmap the kernel va which cause UAF of the kernel…

The cam_get_device_priv 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.

Memory corruption in WLAN while running doDriverCmd for an unspecific command.

Memory corruption in RIL while trying to send apdu packet.

Memory corruption in Trusted Execution Environment while calling service API with invalid address.

Memory corruption in Linux when the file upload API is called with parameters having large buffer.

Memory corruption in Audio while processing sva_model_serializer using memory size passed by HIDL client.

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.

Memory Corruption in Modem due to double free while parsing the PKCS15 sim files.

Memory corruption in Linux while sending DRM request.

Memory corruption due to use after free in Core when multiple DCI clients register and deregister.

Memory corruption in Audio due to incorrect type cast during audio use-cases.

Memory corruption in FM Host due to buffer copy without checking the size of input in FM Host

Memory corruption in Linux android due to double free while calling unregister provider after register call.

Memory corruption due to buffer copy without checking the size of input in Core while processing ioctl commands from diag client applications.

Memory corruption in core due to buffer copy without check9ing the size of input while processing ioctl queries.

Memory corruption due to improper validation of array index in computer vision while testing EVA kernel without sending any frames.

Memory corruption due to improper validation of array index in User Identity Module when APN TLV length is greater than command length.

Memory corruption due to incorrect type conversion or cast in audio while using audio playback/capture when crafted address is sent from AGM IPC to AGM.

Memory corruption due to use after free in Modem while modem initialization.

Information disclosure due to buffer overread in Linux sensors

Memory corruption occurs in Modem due to improper validation of array index when malformed APDU is sent from card.

Memory corruption in WLAN due to use after free

Memory corruption in Audio due to use of out-of-range pointer offset while Initiating a voice call session from user space with invalid session id.

Memory corruption due to use after free in trusted application environment.

Information disclosure in Trusted Execution Environment due to buffer over-read while processing metadata verification requests.

Information disclosure due to buffer overread in Core

Information disclosure due to buffer overread in Core

Memory corruption in video driver due to type confusion error during video playback

Memory corruption in display due to double free while allocating frame buffer memory

Memory corruption in Multimedia Framework due to unsafe access to the data members

Memory corruption in display driver due to incorrect type casting while accessing the fence structure fields

Memory corruption in camera due to buffer copy without checking size of input in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wearables

Memory corruption in camera due to improper validation of array index in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Memory corruption in diag due to use after free while processing dci packet in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Information disclosure in video due to buffer over-read while parsing avi files in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Memory corruption due to use after free in service while trying to access maps by different threads in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Information disclosure due to buffer over read in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile

Memory corruption in kernel due to improper input validation while processing ION commands in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables

Information disclosure in video due to buffer over-read while processing avi file in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Use after free in the synx driver issue while performing other functions during multiple invocation of synx release calls in Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile

Possible address manipulation from APP-NS while APP-S is configuring an RG where it tries to merge the address ranges in Snapdragon Connectivity, Snapdragon Mobile

Improper checking of AP-S lock bit while verifying the secure resource group permissions can lead to non secure read and write access in Snapdragon Connectivity, Snapdragon Mobile

An array index is improperly used to lock and unlock a mutex which can lead to a Use After Free condition In the Synx driver in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile

Improper handling between export and release functions on the same handle from client can lead to use after free in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile