Qxm1096 Firmware
by Qualcomm
CVEs (32)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-24090 | Hig | 0.46 | 7.1 | 0.00 | Jun 1, 2026 | Cryptographic issue while processing partition table entries allows unauthorized modification of boot flow. | ||
| CVE-2025-47378 | Hig | 0.46 | 7.1 | 0.00 | Mar 2, 2026 | Cryptographic Issue when a shared VM reference allows HLOS to boot loader and access cert chain. | ||
| CVE-2025-59610 | Med | 0.42 | 6.4 | 0.00 | Jun 1, 2026 | Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer. | ||
| CVE-2025-47403 | Med | 0.42 | 6.5 | 0.00 | May 4, 2026 | Transient DOS when processing a malformed Fast Transition response frame with an invalid header structure during wireless roaming. | ||
| CVE-2025-47401 | Med | 0.42 | 6.5 | 0.00 | May 4, 2026 | Transient DOS when processing target power rate tables during channel configuration. | ||
| CVE-2025-47374 | Med | 0.42 | 6.5 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling. | ||
| CVE-2026-21384 | Med | 0.00 | 5.3 | 0.00 | Jul 6, 2026 | Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits. | ||
| CVE-2026-21383 | Hig | 0.00 | 7.1 | 0.00 | Jul 6, 2026 | 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 | Med | 0.00 | 5.3 | 0.00 | Jul 6, 2026 | Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values. | ||
| CVE-2026-21369 | Med | 0.00 | 5.3 | 0.00 | Jul 6, 2026 | Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification. | ||
| CVE-2026-21368 | Med | 0.00 | 5.3 | 0.00 | Jul 6, 2026 | Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks. | ||
| CVE-2025-59615 | Med | 0.00 | 6.6 | 0.00 | Jul 6, 2026 | Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization. |
- risk 0.46cvss 7.1epss 0.00
Cryptographic issue while processing partition table entries allows unauthorized modification of boot flow.
- risk 0.46cvss 7.1epss 0.00
Cryptographic Issue when a shared VM reference allows HLOS to boot loader and access cert chain.
- risk 0.42cvss 6.4epss 0.00
Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer.
- risk 0.42cvss 6.5epss 0.00
Transient DOS when processing a malformed Fast Transition response frame with an invalid header structure during wireless roaming.
- risk 0.42cvss 6.5epss 0.00
Transient DOS when processing target power rate tables during channel configuration.
- risk 0.42cvss 6.5epss 0.00
Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling.
- risk 0.00cvss 5.3epss 0.00
Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits.
- risk 0.00cvss 7.1epss 0.00
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
- risk 0.00cvss 5.3epss 0.00
Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.
- risk 0.00cvss 5.3epss 0.00
Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification.
- risk 0.00cvss 5.3epss 0.00
Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks.
- risk 0.00cvss 6.6epss 0.00
Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization.
Page 2 of 2