Chipset
Qualcomm SM6125
Also known as Snapdragon 665
Statistics
Released (est):
April 2019
6 years ago
Vulnerabilities:
86
Devices:
68
Vulnerabilities
| Id | Severity | Component | Affects | Reported on | Published by manufacturer | Published by AOSP |
|---|---|---|---|---|---|---|
| CVE-2023-33017 | HIGH | BOOT | FIRMWARE | N/A | Dec 2023 | Dec 2023 |
| CVE-2023-33018 | HIGH | DEBUG | N/A | N/A | Dec 2023 | Dec 2023 |
| CVE-2023-33022 | HIGH | N/A | OS | N/A | Dec 2023 | Dec 2023 |
| CVE-2023-33054 | CRITICAL | POSITION | OS | Mar 18, 2023 | Dec 2023 | Dec 2023 |
| CVE-2023-33063 | HIGH | N/A | OS | Dec 18, 2022 | Dec 2023 | Dec 2023 |
| CVE-2023-33070 | HIGH | N/A | OS | Nov 17, 2022 | Dec 2023 | N/A |
| CVE-2023-33080 | HIGH | WIFI | FIRMWARE | N/A | Dec 2023 | Dec 2023 |
| CVE-2023-33059 | HIGH | AUDIO | OS | Mar 24, 2023 | Nov 2023 | Nov 2023 |
| CVE-2023-28540 | CRITICAL | CELLULAR | FIRMWARE | N/A | Oct 2023 | Oct 2023 |
| CVE-2023-28560 | HIGH | WIFI | N/A | Jun 10, 2022 | Sep 2023 | Jan 2024 |
86 of 86 row(s) shown.
Rows per page
Page 1 of 9
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| HTC Desire 20 Pro | HTC Desire 20 Pro | HTC | Jul 18, 2020 |
| Sony Xperia 10 II | XQ-AU51 | SONY | May 5, 2020 |
| Sony Xperia 10 II | XQ-AU52 | SONY | May 5, 2020 |
| Sony Xperia 10 II | SO-41A | SONY | May 5, 2020 |
| T-Mobile REVVL 4+ | 5062W | TMOBILE | Sep 4, 2020 |
| T-Mobile REVVL 4+ | 5062Z | TMOBILE | Sep 4, 2020 |
| TCL 20S | T773O | TCL | May 20, 2021 |
| Motorola One Vision Plus | Motorola One Vision Plus | MOTOROLA | Jul 13, 2020 |
| Motorola Moto G Fast | XT2045-3 | MOTOROLA | Jun 12, 2020 |
| Motorola Moto G Pro | XT2043-7 | MOTOROLA | Jun 15, 2020 |
68 of 68 row(s) shown.
Rows per page
Page 1 of 7
Information reliability
The information on this website is intended to provide information on the big picture of chipset security and measure trends within the industry. Our information is obtained from several vantage points, checked for consistency, and automatically cross-referenced. However, this process may not always yield reliable information. Do not use the information on a particular vulnerability, chipset or device to verify your individual exposure in cases where inaccuracies are inacceptable, for instance to assess risks if you are a Politically Exposed Person.
