Qcs610 Firmware
by Qualcomm
CVEs (561)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2019-14119 | Hig | 0.46 | 7.0 | 0.00 | Sep 8, 2020 | u'While processing SMCInvoke asynchronous message header, message count is modified leading to a TOCTOU race condition and lead to memory corruption' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon… | ||
| CVE-2024-33053 | Med | 0.44 | 6.7 | 0.00 | Dec 2, 2024 | Memory corruption when multiple threads try to unregister the CVP buffer at the same time. | ||
| CVE-2024-33036 | Med | 0.44 | 6.7 | 0.00 | Dec 2, 2024 | 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. | ||
| CVE-2021-30299 | Med | 0.44 | 6.7 | 0.00 | Nov 22, 2024 | Possible out of bound access in audio module due to lack of validation of user provided input. | ||
| CVE-2024-33032 | Med | 0.44 | 6.7 | 0.00 | Nov 4, 2024 | Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it. | ||
| CVE-2024-33016 | Med | 0.44 | 6.8 | 0.00 | Sep 2, 2024 | memory corruption when an invalid firehose patch command is invoked. | ||
| CVE-2023-43521 | Med | 0.44 | 6.7 | 0.00 | May 6, 2024 | Memory corruption when multiple listeners are being registered with the same file descriptor. | ||
| CVE-2023-33077 | Med | 0.44 | 6.7 | 0.00 | Feb 6, 2024 | Memory corruption in HLOS while converting from authorization token to HIDL vector. | ||
| CVE-2023-33069 | Med | 0.44 | 6.7 | 0.00 | Feb 6, 2024 | Memory corruption in Audio while processing the calibration data returned from ACDB loader. | ||
| CVE-2023-33068 | Med | 0.44 | 6.7 | 0.00 | Feb 6, 2024 | Memory corruption in Audio while processing IIR config data from AFE calibration block. | ||
| CVE-2023-33067 | Med | 0.44 | 6.7 | 0.00 | Feb 6, 2024 | Memory corruption in Audio while calling START command on host voice PCM multiple times for the same RX or TX tap points. | ||
| CVE-2023-33038 | Med | 0.44 | 6.7 | 0.00 | Jan 2, 2024 | Memory corruption while receiving a message in Bus Socket Transport Server. | ||
| CVE-2023-28580 | Med | 0.44 | 6.7 | 0.00 | Dec 5, 2023 | Memory corruption in WLAN Host while setting the PMK length in PMK length in internal cache. | ||
| CVE-2023-28579 | Med | 0.44 | 6.7 | 0.00 | Dec 5, 2023 | Memory Corruption in WLAN Host while deserializing the input PMK bytes without checking the input PMK length. | ||
| CVE-2023-22383 | Med | 0.44 | 6.7 | 0.00 | Dec 5, 2023 | Memory Corruption in camera while installing a fd for a particular DMA buffer. | ||
| CVE-2023-28570 | Med | 0.44 | 6.7 | 0.00 | Nov 7, 2023 | Memory corruption while processing audio effects. | ||
| CVE-2023-21654 | Med | 0.44 | 6.7 | 0.00 | Sep 5, 2023 | Memory corruption in Audio during playback session with audio effects enabled. | ||
| CVE-2023-28577 | Med | 0.44 | 6.7 | 0.00 | Aug 8, 2023 | 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… | ||
| CVE-2023-28575 | Med | 0.44 | 6.7 | 0.00 | Aug 8, 2023 | 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. | ||
| CVE-2023-21650 | Med | 0.44 | 6.7 | 0.00 | Aug 8, 2023 | Memory Corruption in GPS HLOS Driver when injectFdclData receives data with invalid data length. |
- risk 0.46cvss 7.0epss 0.00
u'While processing SMCInvoke asynchronous message header, message count is modified leading to a TOCTOU race condition and lead to memory corruption' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon…
- risk 0.44cvss 6.7epss 0.00
Memory corruption when multiple threads try to unregister the CVP buffer at the same time.
- risk 0.44cvss 6.7epss 0.00
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.
- risk 0.44cvss 6.7epss 0.00
Possible out of bound access in audio module due to lack of validation of user provided input.
- risk 0.44cvss 6.7epss 0.00
Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.
- risk 0.44cvss 6.8epss 0.00
memory corruption when an invalid firehose patch command is invoked.
- risk 0.44cvss 6.7epss 0.00
Memory corruption when multiple listeners are being registered with the same file descriptor.
- risk 0.44cvss 6.7epss 0.00
Memory corruption in HLOS while converting from authorization token to HIDL vector.
- risk 0.44cvss 6.7epss 0.00
Memory corruption in Audio while processing the calibration data returned from ACDB loader.
- risk 0.44cvss 6.7epss 0.00
Memory corruption in Audio while processing IIR config data from AFE calibration block.
- risk 0.44cvss 6.7epss 0.00
Memory corruption in Audio while calling START command on host voice PCM multiple times for the same RX or TX tap points.
- risk 0.44cvss 6.7epss 0.00
Memory corruption while receiving a message in Bus Socket Transport Server.
- risk 0.44cvss 6.7epss 0.00
Memory corruption in WLAN Host while setting the PMK length in PMK length in internal cache.
- risk 0.44cvss 6.7epss 0.00
Memory Corruption in WLAN Host while deserializing the input PMK bytes without checking the input PMK length.
- risk 0.44cvss 6.7epss 0.00
Memory Corruption in camera while installing a fd for a particular DMA buffer.
- risk 0.44cvss 6.7epss 0.00
Memory corruption while processing audio effects.
- risk 0.44cvss 6.7epss 0.00
Memory corruption in Audio during playback session with audio effects enabled.
- risk 0.44cvss 6.7epss 0.00
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…
- risk 0.44cvss 6.7epss 0.00
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.
- risk 0.44cvss 6.7epss 0.00
Memory Corruption in GPS HLOS Driver when injectFdclData receives data with invalid data length.
Page 23 of 29