Qcs410 Firmware
by Qualcomm
CVEs (536)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2020-11171 | Cri | 0.59 | 9.1 | 0.01 | Mar 17, 2021 | Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice &… | ||
| CVE-2020-11166 | Cri | 0.59 | 9.1 | 0.01 | Mar 17, 2021 | Potential out of bound read exception when UE receives unusually large number of padding octets in the beginning of ROHC header in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile,… | ||
| CVE-2020-11276 | Cri | 0.59 | 9.1 | 0.01 | Feb 22, 2021 | Possible buffer over read while processing P2P IE and NOA attribute of beacon and probe response frames due to improper validation of P2P IE and NOA attribute lengths in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity,… | ||
| CVE-2020-11275 | Cri | 0.59 | 9.1 | 0.01 | Feb 22, 2021 | Possible buffer over-read while parsing quiet IE in Rx beacon frame due to improper check of IE length in received beacon in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial… | ||
| CVE-2020-11177 | Hig | 0.57 | 8.8 | 0.00 | Feb 22, 2021 | User can overwrite Security Code NV item without knowing current SPC due to improper validation of SPC code setting and device lock in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon… | ||
| CVE-2024-33056 | Hig | 0.55 | 8.4 | 0.00 | Dec 2, 2024 | Memory corruption when allocating and accessing an entry in an SMEM partition continuously. | ||
| CVE-2024-33044 | Hig | 0.55 | 8.4 | 0.00 | Dec 2, 2024 | Memory corruption while Configuring the SMR/S2CR register in Bypass mode. | ||
| CVE-2024-33060 | Hig | 0.55 | 8.4 | 0.00 | Sep 2, 2024 | Memory corruption when two threads try to map and unmap a single node simultaneously. | ||
| CVE-2024-33045 | Hig | 0.55 | 8.4 | 0.00 | Sep 2, 2024 | Memory corruption when BTFM client sends new messages over Slimbus to ADSP. | ||
| CVE-2024-33028 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released. | ||
| CVE-2024-33027 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table. | ||
| CVE-2024-33023 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events. | ||
| CVE-2024-33022 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption while allocating memory in HGSL driver. | ||
| CVE-2024-33021 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption while processing IOCTL call to set metainfo. | ||
| CVE-2024-23373 | Hig | 0.55 | 8.4 | 0.00 | Jul 1, 2024 | Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released. | ||
| CVE-2024-21461 | Hig | 0.55 | 8.4 | 0.00 | Jul 1, 2024 | Memory corruption while performing finish HMAC operation when context is freed by keymaster. | ||
| CVE-2024-21471 | Hig | 0.55 | 8.4 | 0.00 | May 6, 2024 | Memory corruption when IOMMU unmap of a GPU buffer fails in Linux. | ||
| CVE-2024-21468 | Hig | 0.55 | 8.4 | 0.00 | Apr 1, 2024 | Memory corruption when there is failed unmap operation in GPU. | ||
| CVE-2023-33023 | Hig | 0.55 | 8.4 | 0.00 | Apr 1, 2024 | Memory corruption while processing finish_sign command to pass a rsp buffer. | ||
| CVE-2023-28547 | Hig | 0.55 | 8.4 | 0.00 | Apr 1, 2024 | Memory corruption in SPS Application while requesting for public key in sorter TA. |
- risk 0.59cvss 9.1epss 0.01
Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice &…
- risk 0.59cvss 9.1epss 0.01
Potential out of bound read exception when UE receives unusually large number of padding octets in the beginning of ROHC header in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile,…
- risk 0.59cvss 9.1epss 0.01
Possible buffer over read while processing P2P IE and NOA attribute of beacon and probe response frames due to improper validation of P2P IE and NOA attribute lengths in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity,…
- risk 0.59cvss 9.1epss 0.01
Possible buffer over-read while parsing quiet IE in Rx beacon frame due to improper check of IE length in received beacon in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial…
- risk 0.57cvss 8.8epss 0.00
User can overwrite Security Code NV item without knowing current SPC due to improper validation of SPC code setting and device lock in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon…
- risk 0.55cvss 8.4epss 0.00
Memory corruption when allocating and accessing an entry in an SMEM partition continuously.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while Configuring the SMR/S2CR register in Bypass mode.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when two threads try to map and unmap a single node simultaneously.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when BTFM client sends new messages over Slimbus to ADSP.
- risk 0.55cvss 8.4epss 0.00
Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.
- risk 0.55cvss 8.4epss 0.00
Memory corruption can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while allocating memory in HGSL driver.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while processing IOCTL call to set metainfo.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while performing finish HMAC operation when context is freed by keymaster.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when IOMMU unmap of a GPU buffer fails in Linux.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when there is failed unmap operation in GPU.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while processing finish_sign command to pass a rsp buffer.
- risk 0.55cvss 8.4epss 0.00
Memory corruption in SPS Application while requesting for public key in sorter TA.
Page 4 of 27