This page was not yet optimized for use on mobile devices.
Qualcomm SM8475P Firmware
Configuration details
| CPE title | Qualcomm SM8475P Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:sm8475p_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
74 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2021-35083 | CRITICAL | 9.1 | 14.06.2022 | |
| CVE-2021-35102 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2021-35108 | MEDIUM | 6.8 | 02.09.2022 | |
| CVE-2021-35109 | MEDIUM | 6.8 | 02.09.2022 | |
| CVE-2021-35111 | MEDIUM | 5.9 | 14.06.2022 | |
| CVE-2021-35118 | MEDIUM | 6.7 | 14.06.2022 | |
| CVE-2021-35119 | MEDIUM | 5.5 | 14.06.2022 | |
| CVE-2021-35120 | MEDIUM | 6.7 | 14.06.2022 | |
| CVE-2021-35133 | MEDIUM | 6.7 | 02.09.2022 | |
| CVE-2021-35134 | HIGH | 8.4 | 02.09.2022 | |
| CVE-2022-22059 | HIGH | 7.8 | 02.09.2022 | |
| CVE-2022-22061 | HIGH | 7.8 | 02.09.2022 | |
| CVE-2022-22062 | CRITICAL | 9.1 | 02.09.2022 | |
| CVE-2022-22066 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-22067 | HIGH | 7.8 | 02.09.2022 | |
| CVE-2022-22070 | HIGH | 7.8 | 02.09.2022 | |
| CVE-2022-22074 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-22081 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-22082 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2022-22083 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2022-22084 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2022-22085 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2022-22086 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2022-22087 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2022-22089 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-22090 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2022-22091 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-22092 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-22093 | HIGH | 7.0 | 16.09.2022 | |
| CVE-2022-22094 | HIGH | 7.0 | 16.09.2022 | |
| CVE-2022-22096 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25653 | MEDIUM | 5.5 | 16.09.2022 | |
| CVE-2022-25656 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-25657 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25658 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25659 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25668 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25669 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-25670 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-25686 | CRITICAL | 9.8 | 16.09.2022 | |
| CVE-2022-25688 | CRITICAL | 9.8 | 16.09.2022 | |
| CVE-2022-25693 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-25696 | HIGH | 7.0 | 16.09.2022 | |
| CVE-2022-25706 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2025-47323 | HIGH | 7.8 | 18.12.2025 | |
| CVE-2025-47330 | MEDIUM | 5.5 | 07.01.2026 | |
| CVE-2025-47331 | MEDIUM | 6.1 | 07.01.2026 | |
| CVE-2025-47332 | MEDIUM | 6.4 | 07.01.2026 | |
| CVE-2025-47333 | MEDIUM | 6.6 | 07.01.2026 | |
| CVE-2025-47334 | MEDIUM | 6.7 | 07.01.2026 | |
| CVE-2025-47348 | HIGH | 7.8 | 07.01.2026 | |
| CVE-2025-47366 | HIGH | 7.8 | 02.02.2026 | |
| CVE-2025-47369 | MEDIUM | 5.5 | 07.01.2026 | |
| CVE-2025-47371 | MEDIUM | 6.5 | 02.03.2026 | |
| CVE-2025-47373 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-47383 | HIGH | 7.2 | 02.03.2026 | |
| CVE-2025-47391 | HIGH | 7.8 | 06.04.2026 | |
| CVE-2025-47392 | HIGH | 8.8 | 06.04.2026 | |
| CVE-2025-47397 | HIGH | 7.8 | 02.02.2026 | |
| CVE-2025-47398 | HIGH | 7.8 | 02.02.2026 | |
| CVE-2025-47401 | HIGH | 7.5 | 04.05.2026 | |
| CVE-2025-47403 | HIGH | 7.5 | 04.05.2026 | |
| CVE-2025-59604 | HIGH | 7.8 | 01.06.2026 | |
| CVE-2025-59605 | HIGH | 7.8 | 01.06.2026 | |
| CVE-2025-59610 | MEDIUM | 6.4 | 01.06.2026 | |
| CVE-2026-21367 | HIGH | 7.5 | 06.04.2026 | |
| CVE-2026-21385 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2026-24077 | MEDIUM | 6.5 | 04.08.2026 | |
| CVE-2026-24078 | MEDIUM | 6.5 | 04.08.2026 | |
| CVE-2026-24079 | HIGH | 8.1 | 04.08.2026 | |
| CVE-2026-24084 | HIGH | 7.5 | 04.08.2026 | |
| CVE-2026-24085 | HIGH | 7.2 | 01.06.2026 | |
| CVE-2026-24088 | HIGH | 8.2 | 01.06.2026 | |
| CVE-2026-24091 | HIGH | 7.2 | 01.06.2026 |
Showing 5 out of 74.
Matched certificates
This CPE has no matched certificates.