Sc8380xp Firmware
by Qualcomm
CVEs (257)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-57537 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization. | ||
| CVE-2026-25291 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms. | ||
| CVE-2026-25267 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory corruption when non-secure loader rewrites page tables before secure memory initialization. | ||
| CVE-2026-25280 | Hig | 0.51 | 7.8 | 0.00 | Sep 17, 2026 | Memory corruption when processing escape handling flow with insufficient user buffer sizes. | ||
| CVE-2026-24075 | Hig | 0.51 | 7.8 | 0.00 | Sep 17, 2026 | Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions. | ||
| CVE-2026-24074 | Hig | 0.51 | 7.8 | 0.00 | Sep 17, 2026 | Memory Corruption when processing data with large offset and length values exceeds buffer limits during data copy operations. | ||
| CVE-2026-24073 | Hig | 0.51 | 7.8 | 0.00 | Sep 17, 2026 | Memory corruption when processing decode statistics due to insufficient validation of offset against structure size. | ||
| CVE-2025-59607 | Hig | 0.51 | 7.8 | 0.00 | Sep 17, 2026 | Memory Corruption when copying large input data exceeds normal allocation limits. | ||
| CVE-2026-25260 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications. | ||
| CVE-2026-25259 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory corruption while processing multiple IOCTL command for escape operations. | ||
| CVE-2026-25258 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory corruption while processing IOCTL calls for escape operations. | ||
| CVE-2025-59604 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. | ||
| CVE-2025-47408 | Hig | 0.51 | 7.8 | 0.00 | May 4, 2026 | Memory corruption when another driver calls an IOCTL with invalid input/output buffer. | ||
| CVE-2025-47407 | Hig | 0.51 | 7.8 | 0.00 | May 4, 2026 | Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level. | ||
| CVE-2025-47405 | Hig | 0.51 | 7.8 | 0.00 | May 4, 2026 | Memory corruption when processing camera sensor input/output control codes with invalid output buffers. | ||
| CVE-2026-21382 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when handling power management requests with improperly sized input/output buffers. | ||
| CVE-2026-21380 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when using deprecated DMABUF IOCTL calls to manage video memory. | ||
| CVE-2026-21378 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver. | ||
| CVE-2026-21376 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver. | ||
| CVE-2026-21375 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing. |
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when non-secure loader rewrites page tables before secure memory initialization.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when processing escape handling flow with insufficient user buffer sizes.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when processing data with large offset and length values exceeds buffer limits during data copy operations.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when processing decode statistics due to insufficient validation of offset against structure size.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when copying large input data exceeds normal allocation limits.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing multiple IOCTL command for escape operations.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing IOCTL calls for escape operations.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when another driver calls an IOCTL with invalid input/output buffer.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when processing camera sensor input/output control codes with invalid output buffers.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when handling power management requests with improperly sized input/output buffers.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when using deprecated DMABUF IOCTL calls to manage video memory.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing.
Page 3 of 13