This page was not yet optimized for use on mobile devices.
Qualcomm SM7675P Firmware
Configuration details
| CPE title | Qualcomm SM7675P Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:sm7675p_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
135 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2024-33058 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2024-38404 | HIGH | 7.5 | 03.02.2025 | |
| CVE-2024-38426 | MEDIUM | 5.3 | 03.03.2025 | |
| CVE-2024-43046 | MEDIUM | 5.5 | 07.04.2025 | |
| CVE-2024-43051 | MEDIUM | 5.5 | 03.03.2025 | |
| CVE-2024-43056 | MEDIUM | 6.5 | 03.03.2025 | |
| CVE-2024-43065 | HIGH | 7.1 | 07.04.2025 | |
| CVE-2024-45549 | HIGH | 7.7 | 07.04.2025 | |
| CVE-2024-45551 | MEDIUM | 6.2 | 07.04.2025 | |
| CVE-2024-45553 | HIGH | 7.8 | 06.01.2025 | |
| CVE-2024-45558 | HIGH | 7.5 | 06.01.2025 | |
| CVE-2024-45569 | CRITICAL | 9.8 | 03.02.2025 | |
| CVE-2024-45571 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-45582 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-45584 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49833 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49834 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49835 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49838 | HIGH | 7.5 | 03.02.2025 | |
| CVE-2024-49839 | CRITICAL | 9.8 | 03.02.2025 | |
| CVE-2024-49843 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49844 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49845 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49847 | HIGH | 7.5 | 06.05.2025 | |
| CVE-2024-49848 | MEDIUM | 6.7 | 07.04.2025 | |
| CVE-2024-53011 | HIGH | 7.9 | 03.03.2025 | |
| CVE-2024-53014 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2024-53015 | MEDIUM | 6.6 | 03.06.2025 | |
| CVE-2024-53019 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53020 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53021 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53024 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2024-53026 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53027 | HIGH | 7.5 | 03.03.2025 | |
| CVE-2025-21422 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-21424 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2025-21432 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-21433 | MEDIUM | 5.5 | 08.07.2025 | |
| CVE-2025-21434 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21446 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-21448 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21449 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-21450 | CRITICAL | 9.1 | 08.07.2025 | |
| CVE-2025-21453 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2025-21454 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-21459 | HIGH | 7.5 | 06.05.2025 | |
| CVE-2025-21461 | HIGH | 7.8 | 06.08.2025 | |
| CVE-2025-21463 | HIGH | 7.5 | 03.06.2025 | |
| CVE-2025-21464 | MEDIUM | 6.5 | 06.08.2025 | |
| CVE-2025-21465 | MEDIUM | 6.5 | 06.08.2025 | |
| CVE-2025-21468 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2025-21476 | HIGH | 7.8 | 24.09.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-21487 | HIGH | 8.2 | 24.09.2025 | |
| CVE-2025-21488 | HIGH | 8.2 | 24.09.2025 | |
| CVE-2025-27032 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-27033 | MEDIUM | 6.1 | 24.09.2025 | |
| CVE-2025-27034 | CRITICAL | 9.8 | 24.09.2025 | |
| CVE-2025-27042 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27043 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27052 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27053 | HIGH | 7.8 | 09.10.2025 | |
| CVE-2025-27054 | HIGH | 7.8 | 09.10.2025 | |
| CVE-2025-27057 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-27061 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27062 | HIGH | 7.8 | 06.08.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-27073 | HIGH | 7.5 | 06.08.2025 | |
| CVE-2025-47317 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-47319 | MEDIUM | 6.7 | 18.12.2025 | |
| CVE-2025-47320 | HIGH | 7.8 | 18.12.2025 | |
| 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-47335 | MEDIUM | 6.7 | 07.01.2026 | |
| CVE-2025-47337 | MEDIUM | 6.7 | 07.01.2026 | |
| CVE-2025-47339 | HIGH | 7.8 | 07.01.2026 | |
| CVE-2025-47344 | MEDIUM | 6.4 | 07.01.2026 | |
| CVE-2025-47345 | HIGH | 8.4 | 07.01.2026 | |
| CVE-2025-47346 | HIGH | 7.8 | 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-47370 | MEDIUM | 6.5 | 04.11.2025 | |
| CVE-2025-47371 | MEDIUM | 6.5 | 02.03.2026 | |
| CVE-2025-47373 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-47375 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-47376 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-47377 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-47379 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-47382 | HIGH | 7.8 | 18.12.2025 | |
| CVE-2025-47383 | HIGH | 7.2 | 02.03.2026 | |
| CVE-2025-47386 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-47389 | HIGH | 7.8 | 06.04.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-47402 | MEDIUM | 6.5 | 02.02.2026 | |
| CVE-2025-47403 | HIGH | 7.5 | 04.05.2026 | |
| CVE-2025-47404 | HIGH | 7.8 | 04.05.2026 | |
| CVE-2025-59600 | HIGH | 7.8 | 02.03.2026 | |
| CVE-2025-59604 | HIGH | 7.8 | 01.06.2026 | |
| CVE-2025-59609 | MEDIUM | 5.5 | 01.06.2026 | |
| CVE-2025-59610 | MEDIUM | 6.4 | 01.06.2026 | |
| CVE-2026-21367 | HIGH | 7.5 | 06.04.2026 | |
| CVE-2026-21381 | 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-24081 | HIGH | 7.4 | 17.09.2026 | |
| CVE-2026-24082 | HIGH | 7.8 | 04.05.2026 | |
| CVE-2026-24084 | HIGH | 7.5 | 04.08.2026 | |
| CVE-2026-24085 | HIGH | 7.2 | 01.06.2026 | |
| CVE-2026-24087 | HIGH | 7.2 | 01.06.2026 | |
| CVE-2026-24088 | HIGH | 8.2 | 01.06.2026 | |
| CVE-2026-24089 | HIGH | 7.2 | 01.06.2026 | |
| CVE-2026-24090 | HIGH | 7.1 | 01.06.2026 | |
| CVE-2026-24091 | HIGH | 7.2 | 01.06.2026 | |
| CVE-2026-24092 | HIGH | 7.2 | 01.06.2026 | |
| CVE-2026-25275 | HIGH | 7.5 | 17.09.2026 | |
| CVE-2026-25289 | CRITICAL | 9.6 | 04.08.2026 | |
| CVE-2026-25294 | HIGH | 7.4 | 17.09.2026 |
Showing 5 out of 135.
Matched certificates
This CPE has no matched certificates.