Snapdragon 8\+ Gen 2 Mobile Platform Firmware
by Qualcomm
CVEs (217)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2023-21673 | Hig | 0.57 | 8.7 | 0.00 | Oct 3, 2023 | Improper Access to the VM resource manager can lead to Memory Corruption. | ||
| CVE-2023-43534 | Hig | 0.56 | 8.6 | 0.00 | Feb 6, 2024 | Memory corruption while validating the TID to Link Mapping action request frame, when a station connects to an access point. | ||
| CVE-2023-43520 | Hig | 0.56 | 8.6 | 0.00 | Feb 6, 2024 | Memory corruption when AP includes TID to link mapping IE in the beacons and STA is parsing the beacon TID to link mapping IE. | ||
| 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-23365 | Hig | 0.55 | 8.4 | 0.00 | Sep 2, 2024 | Memory corruption while releasing shared resources in MinkSocket listener thread. | ||
| CVE-2024-33034 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time. | ||
| 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-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-23384 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption when the mapped pages in VBO are still mapped after reclaiming by shrinker. | ||
| CVE-2024-23382 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption while processing graphics kernel driver request to create DMA fence. | ||
| CVE-2024-21481 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption when preparing a shared memory notification for a memparcel in Resource Manager. | ||
| CVE-2024-23380 | Hig | 0.55 | 8.4 | 0.00 | Jul 1, 2024 | Memory corruption while handling user packets during VBO bind operation. | ||
| 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-23372 | Hig | 0.55 | 8.4 | 0.00 | Jul 1, 2024 | Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size. | ||
| 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-2023-43514 | Hig | 0.55 | 8.4 | 0.00 | Jan 2, 2024 | Memory corruption while invoking IOCTLs calls from user space for internal mem MAP and internal mem UNMAP. | ||
| CVE-2023-33113 | Hig | 0.55 | 8.4 | 0.00 | Jan 2, 2024 | Memory corruption when resource manager sends the host kernel a reply message with multiple fragments. | ||
| CVE-2023-33094 | Hig | 0.55 | 8.4 | 0.00 | Jan 2, 2024 | Memory corruption while running VK synchronization with KASAN enabled. |
- risk 0.57cvss 8.7epss 0.00
Improper Access to the VM resource manager can lead to Memory Corruption.
- risk 0.56cvss 8.6epss 0.00
Memory corruption while validating the TID to Link Mapping action request frame, when a station connects to an access point.
- risk 0.56cvss 8.6epss 0.00
Memory corruption when AP includes TID to link mapping IE in the beacons and STA is parsing the beacon TID to link mapping IE.
- 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 releasing shared resources in MinkSocket listener thread.
- risk 0.55cvss 8.4epss 0.00
Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time.
- 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 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 the mapped pages in VBO are still mapped after reclaiming by shrinker.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while processing graphics kernel driver request to create DMA fence.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when preparing a shared memory notification for a memparcel in Resource Manager.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while handling user packets during VBO bind operation.
- 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 invoking IOCTL call for GPU memory allocation and size param is greater than expected size.
- 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 while invoking IOCTLs calls from user space for internal mem MAP and internal mem UNMAP.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when resource manager sends the host kernel a reply message with multiple fragments.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while running VK synchronization with KASAN enabled.
Page 2 of 11