Sar2130p Firmware (Qualcomm) - vulnerabilities (CVEs)

36 CVEs, 6 in the last 30 days, 1 known versions, newest CVE from 2026-10-06. Vendor: Qualcomm.

CVEs of Sar2130p Firmware

• CVE-2026-57554 - CVSS 7.8 (high), 2026-10-06: Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations.
• 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-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-25275 - CVSS 7.5 (high), 2026-09-17: Transient DOS when processing authentication frames with invalid FILS information element header lengths.
• CVE-2026-24081 - CVSS 7.4 (high), 2026-09-17: Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled.
• CVE-2026-25289 - CVSS 9.6 (critical), 2026-08-04: Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values.
• CVE-2026-25268 - CVSS 8.8 (high), 2026-07-06: Memory Corruption when processing invalid HT40 channel layouts during dynamic channel switching operations.
• 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-21383 - CVSS 7.1 (high), 2026-07-06: Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
• 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-24092 - CVSS 7.2 (high), 2026-06-01: Memory Corruption when processing fastboot commands to set display mode.
• CVE-2026-24091 - CVSS 7.2 (high), 2026-06-01: Memory corruption while processing fastboot commands with improperly formatted 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-24085 - CVSS 7.2 (high), 2026-06-01: Memory Corruption when processing display command line information due to improper initialization of a variable.
• 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-59609 - CVSS 5.5 (medium), 2026-06-01: Information Disclosure when processing advertisement frames with malformed MBSSID elements of insufficient length.
• 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.
• CVE-2025-59605 - CVSS 7.8 (high), 2026-06-01: Memory Corruption when processing device identifier strings that exceed the expected maximum length.
• CVE-2025-47407 - CVSS 7.8 (high), 2026-05-04: Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level.
• CVE-2025-47403 - CVSS 7.5 (high), 2026-05-04: Transient DOS when processing a malformed Fast Transition response frame with an invalid header structure during wireless roaming.
• CVE-2025-47401 - CVSS 7.5 (high), 2026-05-04: Transient DOS when processing target power rate tables during channel configuration.
• CVE-2026-21381 - CVSS 7.6 (high), 2026-04-06: Transient DOS when receiving a service data frame with excessive length during device matching over a neighborhood awareness network protocol connection.
• CVE-2026-21367 - CVSS 7.6 (high), 2026-04-06: Transient DOS when processing nonstandard FILS Discovery Frames with out-of-range action sizes during initial scans.
• CVE-2025-47374 - CVSS 6.5 (medium), 2026-04-06: Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling.
• CVE-2026-21385 - CVSS 7.8 (high), 2026-03-02: Memory corruption while using alignments for memory allocation.
• CVE-2025-59600 - CVSS 7.8 (high), 2026-03-02: Memory Corruption when adding user-supplied data without checking available buffer space.
• CVE-2025-47378 - CVSS 7.1 (high), 2026-03-02: Cryptographic Issue when a shared VM reference allows HLOS to boot loader and access cert chain.
• CVE-2025-47373 - CVSS 7.8 (high), 2026-03-02: Memory Corruption when accessing buffers with invalid length during TA invocation.
• CVE-2025-47397 - CVSS 7.8 (high), 2026-02-02: Memory Corruption when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors.
• CVE-2025-47402 - CVSS 6.5 (medium), 2026-02-02: Transient DOS when processing a received frame with an excessively large authentication information element.
• CVE-2025-47398 - CVSS 7.8 (high), 2026-02-02: Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers.