Chipset
Qualcomm SDM632
Also known as Snapdragon 632
Statistics
Released (est):
July 2018
6 years ago
Vulnerabilities:
284
Devices:
21
Vulnerabilities
| Id | Severity | Component | Affects | Reported on | Published by manufacturer | Published by AOSP |
|---|---|---|---|---|---|---|
| CVE-2018-5383 | HIGH | BLUETOOTH | FIRMWARE | Jan 18, 2018 | Apr 2024 | Aug 2018 |
| CVE-2020-11123 | HIGH | TRUST | OS | Dec 4, 2019 | Nov 2020 | Nov 2020 |
| CVE-2020-11168 | HIGH | GPU | N/A | N/A | Nov 2020 | Nov 2020 |
| CVE-2020-11193 | HIGH | GPU | N/A | N/A | Nov 2020 | Nov 2020 |
| CVE-2020-11196 | HIGH | GPU | N/A | N/A | Nov 2020 | Nov 2020 |
| CVE-2020-3639 | CRITICAL | CELLULAR | FIRMWARE | N/A | Nov 2020 | Nov 2020 |
| CVE-2020-11125 | N/A | IPC | OS | N/A | Oct 2020 | Oct 2020 |
| CVE-2020-11157 | N/A | BLUETOOTH | N/A | N/A | Oct 2020 | Oct 2020 |
| CVE-2020-11162 | N/A | IPC | OS | N/A | Oct 2020 | Oct 2020 |
| CVE-2020-11173 | N/A | N/A | OS | Mar 16, 2020 | Oct 2020 | Oct 2020 |
284 of 284 row(s) shown.
Rows per page
Page 1 of 29
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| Asus Zenfone Max (M2) ZB633KL | X01AD | ASUS | Dec 1, 2018 |
| Asus Zenfone Max (M2) ZB633KL | X01BD | ASUS | Dec 1, 2018 |
| Fairphone 3+ | Fairphone 3+ | FAIRPHONE | Sep 14, 2020 |
| Fairphone 3 | Fairphone 3 | FAIRPHONE | Sep 3, 2019 |
| Meizu Note 8 | Meizu Note 8 | MEIZU | Nov 1, 2018 |
| T-Mobile Revvlry | T-Mobile Revvlry | TMOBILE | Jul 1, 2019 |
| Motorola Moto E (2020) | XT2052DL | MOTOROLA | Jun 10, 2020 |
| Motorola Moto G7 | XT1962 | MOTOROLA | Mar 1, 2019 |
| Motorola Moto G7 | XT1962-4 | MOTOROLA | Mar 1, 2019 |
| Motorola Moto G7 Power | XT1955 | MOTOROLA | Feb 15, 2019 |
21 of 21 row(s) shown.
Rows per page
Page 1 of 3
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.
