Sdr753 Firmware (Qualcomm) - vulnerabilities (CVEs)
23 CVEs, 6 in the last 30 days, 1 known versions, newest CVE from 2026-10-06. Vendor: Qualcomm.
CVEs of Sdr753 Firmware
- CVE-2026-57545 - CVSS 7.8 (high), 2026-10-06: Memory corruption when processing draw objects of incorrect type during graphics command list execution.
- CVE-2026-57537 - CVSS 7.8 (high), 2026-10-06: Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization.
- CVE-2026-25302 - CVSS 7.1 (high), 2026-10-06: Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted…
- CVE-2026-25272 - CVSS 6.7 (medium), 2026-10-06: Memory Corruption when processing camera CRE driver operations with improper handling of buffer limits during hardware update preparation.
- CVE-2026-25270 - CVSS 6.7 (medium), 2026-10-06: Memory corruption when processing command buffer requests with invalid length parameters in the Android Camera driver.
- CVE-2026-25269 - CVSS 6.7 (medium), 2026-10-06: Memory corruption when processing camera requests with excessive batch and IO buffer configurations exceeds allocated memory size.
- CVE-2026-25292 - CVSS 7.6 (high), 2026-08-04: Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration.
- CVE-2026-21384 - CVSS 5.3 (medium), 2026-07-06: Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits.
- CVE-2026-21370 - CVSS 5.3 (medium), 2026-07-06: Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.
- CVE-2026-21369 - CVSS 5.3 (medium), 2026-07-06: Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification.
- CVE-2026-21368 - CVSS 5.3 (medium), 2026-07-06: Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks.
- CVE-2026-25277 - CVSS 8.8 (high), 2026-06-01: Memory corruption while using Strongbox due to buffer overflow.
- CVE-2026-25276 - CVSS 8.8 (high), 2026-06-01: Memory corruption while using Strongbox due to missing bounds check.
- CVE-2026-24092 - CVSS 7.2 (high), 2026-06-01: Memory Corruption when processing fastboot commands to set display mode.
- CVE-2026-24087 - CVSS 7.2 (high), 2026-06-01: Memory corruption while processing fastboot OEM commands.
- CVE-2026-24090 - CVSS 7.1 (high), 2026-06-01: Cryptographic issue while processing partition table entries allows unauthorized modification of boot flow.
- CVE-2026-24085 - CVSS 7.2 (high), 2026-06-01: Memory Corruption when processing display command line information due to improper initialization of a variable.
- CVE-2026-24089 - CVSS 7.2 (high), 2026-06-01: Memory corruption while processing fastboot commands with invalid input.
- CVE-2026-24088 - CVSS 8.2 (high), 2026-06-01: Cryptographic Issue while processing a specific partition which allows unauthorized write access to load a customized bootloader.
- CVE-2026-24091 - CVSS 7.2 (high), 2026-06-01: Memory corruption while processing fastboot commands with improperly formatted input.
- CVE-2025-59610 - CVSS 6.4 (medium), 2026-06-01: Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer.
- CVE-2025-59606 - CVSS 7.8 (high), 2026-06-01: Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization.
- CVE-2025-59604 - CVSS 7.8 (high), 2026-06-01: Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer.