This page was not yet optimized for use on mobile devices.
Qualcomm Snapdragon 870 5g Mobile Platform (sm8250-ac) Firmware
Configuration details
| CPE title | Qualcomm Snapdragon 870 5g Mobile Platform (sm8250-ac) Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:snapdragon_870_5g_mobile_platform_\(sm8250-ac\)_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
68 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2024-21459 | HIGH | 7.5 | 05.08.2024 | |
| CVE-2024-21467 | HIGH | 7.5 | 05.08.2024 | |
| CVE-2024-21479 | HIGH | 7.5 | 05.08.2024 | |
| CVE-2024-21481 | HIGH | 8.4 | 05.08.2024 | |
| CVE-2024-23352 | HIGH | 7.5 | 05.08.2024 | |
| CVE-2024-23353 | HIGH | 7.5 | 05.08.2024 | |
| CVE-2024-23355 | HIGH | 7.8 | 05.08.2024 | |
| CVE-2024-23356 | HIGH | 7.8 | 05.08.2024 | |
| CVE-2024-23359 | HIGH | 8.2 | 02.09.2024 | |
| CVE-2024-23362 | HIGH | 7.1 | 02.09.2024 | |
| CVE-2024-23364 | HIGH | 7.5 | 02.09.2024 | |
| CVE-2024-23369 | HIGH | 7.8 | 07.10.2024 | |
| CVE-2024-33016 | MEDIUM | 6.8 | 02.09.2024 | |
| CVE-2024-33035 | HIGH | 8.4 | 02.09.2024 | |
| CVE-2024-33058 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2024-33069 | HIGH | 7.5 | 07.10.2024 | |
| CVE-2024-43046 | MEDIUM | 5.5 | 07.04.2025 | |
| CVE-2024-43065 | HIGH | 7.1 | 07.04.2025 | |
| CVE-2024-43066 | HIGH | 7.8 | 07.04.2025 | |
| CVE-2024-43067 | HIGH | 7.8 | 07.04.2025 | |
| CVE-2024-45540 | MEDIUM | 6.6 | 07.04.2025 | |
| CVE-2024-45543 | MEDIUM | 6.6 | 07.04.2025 | |
| CVE-2024-45544 | MEDIUM | 6.6 | 07.04.2025 | |
| CVE-2024-45549 | HIGH | 7.7 | 07.04.2025 | |
| CVE-2024-45551 | MEDIUM | 6.2 | 07.04.2025 | |
| CVE-2024-45552 | HIGH | 8.2 | 07.04.2025 | |
| CVE-2024-53010 | HIGH | 7.8 | 03.06.2025 | |
| CVE-2024-53013 | MEDIUM | 6.6 | 03.06.2025 | |
| CVE-2024-53015 | MEDIUM | 6.6 | 03.06.2025 | |
| CVE-2024-53016 | MEDIUM | 6.6 | 03.06.2025 | |
| CVE-2024-53020 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53021 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53026 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2025-21429 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21430 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21435 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21448 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21452 | HIGH | 7.5 | 06.08.2025 | |
| CVE-2025-21455 | HIGH | 7.8 | 06.08.2025 | |
| CVE-2025-21464 | MEDIUM | 6.5 | 06.08.2025 | |
| CVE-2025-21465 | MEDIUM | 6.5 | 06.08.2025 | |
| CVE-2025-21474 | HIGH | 7.8 | 06.08.2025 | |
| CVE-2025-21477 | HIGH | 7.5 | 06.08.2025 | |
| CVE-2025-21479 | HIGH | 8.6 | 03.06.2025 | |
| CVE-2025-21480 | HIGH | 8.6 | 03.06.2025 | |
| CVE-2025-21481 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-21482 | HIGH | 7.1 | 24.09.2025 | |
| CVE-2025-21483 | CRITICAL | 9.8 | 24.09.2025 | |
| CVE-2025-21484 | HIGH | 8.2 | 24.09.2025 | |
| CVE-2025-21487 | HIGH | 8.2 | 24.09.2025 | |
| CVE-2025-27032 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-27034 | CRITICAL | 9.8 | 24.09.2025 | |
| CVE-2025-27037 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-27053 | HIGH | 7.8 | 09.10.2025 | |
| CVE-2025-27054 | HIGH | 7.8 | 09.10.2025 | |
| CVE-2025-27063 | HIGH | 7.8 | 18.12.2025 | |
| CVE-2025-27065 | HIGH | 7.5 | 06.08.2025 | |
| CVE-2025-27066 | HIGH | 7.5 | 06.08.2025 | |
| CVE-2025-27070 | HIGH | 7.8 | 04.11.2025 | |
| CVE-2025-27071 | CRITICAL | 9.8 | 06.08.2025 | |
| CVE-2025-27073 | HIGH | 7.5 | 06.08.2025 | |
| CVE-2025-47318 | HIGH | 7.5 | 24.09.2025 | |
| CVE-2025-47320 | 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-47333 | MEDIUM | 6.6 | 07.01.2026 | |
| CVE-2025-47348 | HIGH | 7.8 | 07.01.2026 | |
| CVE-2025-47369 | MEDIUM | 5.5 | 07.01.2026 |
Showing 5 out of 68.
Matched certificates
This CPE has no matched certificates.