Qcm6490 Firmware
by Qualcomm
CVEs (776)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2020-3703 | Cri | 0.64 | 9.8 | 0.01 | Nov 2, 2020 | u'Buffer over-read issue in Bluetooth peripheral firmware due to lack of check for invalid opcode and length of opcode received from central device(This CVE is equivalent to Link Layer Length Overfow issue (CVE-2019-16336,CVE-2019-17519) and Silent Length Overflow… | ||
| CVE-2020-3692 | Cri | 0.64 | 9.8 | 0.01 | Nov 2, 2020 | u'Possible buffer overflow while updating output buffer for IMEI and Gateway Address due to lack of check of input validation for parameters received from server' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in… | ||
| CVE-2026-21385 | Hig | 0.63 | 7.8 | 0.01 | KEV | Mar 2, 2026 | Memory corruption while using alignments for memory allocation. | |
| CVE-2023-33063 | Hig | 0.63 | 7.8 | 0.01 | KEV | Dec 5, 2023 | Memory corruption in DSP Services during a remote call from HLOS to DSP. | |
| CVE-2020-11261 | Hig | 0.63 | 7.8 | 0.02 | KEV | Jun 9, 2021 | Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice &… | |
| CVE-2025-27038 | Hig | 0.61 | 7.5 | 0.01 | KEV | Jun 3, 2025 | Memory corruption while rendering graphics using Adreno GPU drivers in Chrome. | |
| CVE-2021-30317 | Cri | 0.61 | 9.3 | 0.01 | Feb 11, 2022 | Improper validation of program headers containing ELF metadata can lead to image verification bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon… | ||
| CVE-2023-43556 | Cri | 0.60 | 9.3 | 0.00 | Jun 3, 2024 | Memory corruption in Hypervisor when platform information mentioned is not aligned. | ||
| CVE-2023-28578 | Cri | 0.60 | 9.3 | 0.00 | Mar 4, 2024 | Memory corruption in Core Services while executing the command for removing a single event listener. | ||
| CVE-2023-33072 | Cri | 0.60 | 9.3 | 0.00 | Feb 6, 2024 | Memory corruption in Core while processing control functions. | ||
| CVE-2023-33032 | Cri | 0.60 | 9.3 | 0.00 | Jan 2, 2024 | Memory corruption in TZ Secure OS while requesting a memory allocation from TA region. | ||
| CVE-2023-33030 | Cri | 0.60 | 9.3 | 0.00 | Jan 2, 2024 | Memory corruption in HLOS while running playready use-case. | ||
| CVE-2023-21671 | Cri | 0.60 | 9.3 | 0.00 | Nov 7, 2023 | Memory Corruption in Core during syscall for Sectools Fuse comparison feature. | ||
| CVE-2023-21651 | Cri | 0.60 | 9.3 | 0.00 | Aug 8, 2023 | Memory Corruption in Core due to incorrect type conversion or cast in secure_io_read/write function in TEE. | ||
| CVE-2022-33288 | Cri | 0.60 | 9.3 | 0.00 | Apr 13, 2023 | Memory corruption due to buffer copy without checking the size of input in Core while sending SCM command to get write protection information. | ||
| CVE-2022-33231 | Cri | 0.60 | 9.3 | 0.00 | Apr 13, 2023 | Memory corruption due to double free in core while initializing the encryption key. | ||
| CVE-2022-33257 | Cri | 0.60 | 9.3 | 0.00 | Mar 10, 2023 | Memory corruption in Core due to time-of-check time-of-use race condition during dump collection in trust zone. | ||
| CVE-2022-33232 | Cri | 0.60 | 9.3 | 0.00 | Feb 12, 2023 | Memory corruption due to buffer copy without checking size of input while running memory sharing tests with large scattered memory. | ||
| CVE-2021-35122 | Cri | 0.60 | 9.3 | 0.00 | Sep 2, 2022 | Non-secure region can try modifying RG permissions of IO space xPUs due to improper input validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables | ||
| CVE-2021-35090 | Cri | 0.60 | 9.3 | 0.00 | Jun 14, 2022 | Possible hypervisor memory corruption due to TOC TOU race condition when updating address mappings in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile |
- risk 0.64cvss 9.8epss 0.01
u'Buffer over-read issue in Bluetooth peripheral firmware due to lack of check for invalid opcode and length of opcode received from central device(This CVE is equivalent to Link Layer Length Overfow issue (CVE-2019-16336,CVE-2019-17519) and Silent Length Overflow…
- risk 0.64cvss 9.8epss 0.01
u'Possible buffer overflow while updating output buffer for IMEI and Gateway Address due to lack of check of input validation for parameters received from server' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in…
- risk 0.63cvss 7.8epss 0.01
Memory corruption while using alignments for memory allocation.
- risk 0.63cvss 7.8epss 0.01
Memory corruption in DSP Services during a remote call from HLOS to DSP.
- risk 0.63cvss 7.8epss 0.02
Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice &…
- risk 0.61cvss 7.5epss 0.01
Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.
- risk 0.61cvss 9.3epss 0.01
Improper validation of program headers containing ELF metadata can lead to image verification bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon…
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Hypervisor when platform information mentioned is not aligned.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Core Services while executing the command for removing a single event listener.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Core while processing control functions.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in TZ Secure OS while requesting a memory allocation from TA region.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in HLOS while running playready use-case.
- risk 0.60cvss 9.3epss 0.00
Memory Corruption in Core during syscall for Sectools Fuse comparison feature.
- risk 0.60cvss 9.3epss 0.00
Memory Corruption in Core due to incorrect type conversion or cast in secure_io_read/write function in TEE.
- risk 0.60cvss 9.3epss 0.00
Memory corruption due to buffer copy without checking the size of input in Core while sending SCM command to get write protection information.
- risk 0.60cvss 9.3epss 0.00
Memory corruption due to double free in core while initializing the encryption key.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Core due to time-of-check time-of-use race condition during dump collection in trust zone.
- risk 0.60cvss 9.3epss 0.00
Memory corruption due to buffer copy without checking size of input while running memory sharing tests with large scattered memory.
- risk 0.60cvss 9.3epss 0.00
Non-secure region can try modifying RG permissions of IO space xPUs due to improper input validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- risk 0.60cvss 9.3epss 0.00
Possible hypervisor memory corruption due to TOC TOU race condition when updating address mappings in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
Page 3 of 39