Qualcomm SM8950P Firmware vulnerabilities
8 CVEs affecting Qualcomm SM8950P Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-57546, published 2026-10-06.
More from Qualcomm.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2026-25275, published 2026-09-17. High severity, CVSS 7.5. EPSS: 0.2% chance of exploitation in the next 30 days. Transient DOS when processing authentication frames with invalid FILS information element header lengths.
- CVE-2026-57546, published 2026-10-06. High severity, CVSS 7.5. EPSS: 0.2% chance of exploitation in the next 30 days. Transient DOS when processing a continuous receive command with a zero-sized global configuration override.
- CVE-2026-25294, published 2026-09-17. High severity, CVSS 7.4. EPSS: 0.1% chance of exploitation in the next 30 days. Transient DOS while parsing frame during channel usage.
- CVE-2026-24081, published 2026-09-17. High severity, CVSS 7.4. EPSS: 0.1% chance of exploitation in the next 30 days. Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled.
- CVE-2026-57545, published 2026-10-06. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory corruption when processing draw objects of incorrect type during graphics command list execution.
- CVE-2026-25273, published 2026-10-06. Medium severity, CVSS 6.7. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when processing camera operations due to out-of-bounds write during driver updates.
- CVE-2026-25270, published 2026-10-06. Medium severity, CVSS 6.7. EPSS: 0.1% chance of exploitation in the next 30 days. Memory corruption when processing command buffer requests with invalid length parameters in the Android Camera driver.
- CVE-2026-57537, published 2026-10-06. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization.