Qualcomm
Qualcomm Iqx7181 Firmware: vulnerabilities and CVEs
Qualcomm Iqx7181 Firmware has 22 published vulnerabilities, 22 of them in the last 12 months. 1 are rated critical and 0 are listed by CISA as actively exploited.
CVEs22
Last 12 months22
Critical1
Actively exploited0
All vulnerabilities in the catalogue →⭐ Follow this technology
Latest vulnerabilities
| CVE | Severity | EPSS | Active exploitation | Published | Description |
|---|---|---|---|---|---|
| CVE-2026-25280 | High (7.8) | 0.07% | — | Sep 17, 2026 | Memory corruption when processing escape handling flow with insufficient user buffer sizes. |
| CVE-2026-25275 | High (7.5) | 0.19% | — | Sep 17, 2026 | Transient DOS when processing authentication frames with invalid FILS information element header lengths. |
| CVE-2026-25261 | High (7.8) | 0.07% | — | Sep 17, 2026 | Memory corruption while processing rear sensor IOCTL calls. |
| CVE-2026-24081 | High (7.4) | 0.10% | — | Sep 17, 2026 | Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled. |
| CVE-2026-24075 | High (7) | 0.06% | — | 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 | High (7.8) | 0.07% | — | Sep 17, 2026 | Memory Corruption when processing data with large offset and length values exceeds buffer limits during data copy operations. |
| CVE-2026-24073 | High (7.8) | 0.07% | — | Sep 17, 2026 | Memory corruption when processing decode statistics due to insufficient validation of offset against structure size. |
| CVE-2026-25289 | Critical (9.6) | 0.19% | — | Aug 4, 2026 | Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values. |
| CVE-2026-25271 | High (7) | 0.07% | — | Jul 6, 2026 | Memory Corruption when processing asynchronous input parameters due to improper handling of modified values between check and use. |
| CVE-2026-21379 | High (7.8) | 0.10% | — | Jul 6, 2026 | Memory Corruption when allocating memory with sizes that exceed the maximum allowed value. |
| CVE-2026-25259 | High (7.8) | 0.07% | — | Jun 1, 2026 | Memory corruption while processing multiple IOCTL command for escape operations. |
| CVE-2026-25258 | High (7.8) | 0.07% | — | Jun 1, 2026 | Memory corruption while processing IOCTL calls for escape operations. |
| CVE-2025-59614 | Medium (6.7) | 0.08% | — | Jun 1, 2026 | Memory Corruption when sending random number generator command with insufficient output buffer size. |
| CVE-2025-59613 | Medium (6.7) | 0.08% | — | Jun 1, 2026 | Memory Corruption when output buffer size is smaller than input buffer size during data copying operation. |
| CVE-2025-59612 | Medium (6.7) | 0.08% | — | Jun 1, 2026 | Memory corruption in windows drivers while sending incorrect trusted application request |
| CVE-2025-59611 | Medium (6.7) | 0.08% | — | Jun 1, 2026 | Memory corruption in diagnostic services due to absence of input validation |
| CVE-2025-59604 | High (7.8) | 0.07% | — | Jun 1, 2026 | Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. |
| CVE-2025-47408 | High (7.8) | 0.07% | — | May 4, 2026 | Memory corruption when another driver calls an IOCTL with invalid input/output buffer. |
| CVE-2025-47406 | Medium (5.5) | 0.07% | — | May 4, 2026 | Information Disclosure while processing IOCTL handler callbacks without verifying buffer size. |
| CVE-2025-47405 | High (7.8) | 0.07% | — | May 4, 2026 | Memory corruption when processing camera sensor input/output control codes with invalid output buffers. |
| CVE-2025-47403 | High (7.5) | 0.22% | — | May 4, 2026 | Transient DOS when processing a malformed Fast Transition response frame with an invalid header structure during wireless roaming. |
| CVE-2025-47401 | High (7.5) | 0.22% | — | May 4, 2026 | Transient DOS when processing target power rate tables during channel configuration. |
🎯 How it gets exploited (ATT&CK techniques)
Number of CVEs of this technology mapped to each exploitation or primary-impact technique.