Chipset
Qualcomm MSM8916
Also known as Snapdragon 410
Statistics
Released (est):
January 2014
11 years ago
Vulnerabilities:
94
Devices:
252
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-2021-1924 | CRITICAL | POWER | N/A | N/A | Nov 2021 | Nov 2021 |
| CVE-2021-1909 | HIGH | N/A | N/A | N/A | Sep 2021 | Sep 2021 |
| CVE-2020-11268 | HIGH | CELLULAR | N/A | N/A | May 2021 | N/A |
| CVE-2020-11195 | HIGH | TRUST | OS | Apr 30, 2020 | Feb 2021 | Mar 2021 |
| CVE-2020-11204 | CRITICAL | IPC | N/A | N/A | Feb 2021 | Mar 2021 |
| CVE-2020-11269 | HIGH | WIFI | FIRMWARE | N/A | Feb 2021 | Feb 2021 |
| CVE-2020-11152 | MEDIUM | POSITION | OS | Mar 28, 2019 | Dec 2020 | N/A |
| CVE-2020-11212 | HIGH | WIFI | FIRMWARE | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-11213 | HIGH | WIFI | FIRMWARE | N/A | Dec 2020 | Dec 2020 |
94 of 94 row(s) shown.
Rows per page
Page 1 of 10
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| Coolpad Torino S | Coolpad Torino S | COOLPAD | Mar 1, 2016 |
| Asus Zenfone Go ZB500KL | X00AD | ASUS | Oct 1, 2016 |
| Asus Zenfone Go ZB500KL | X00BD | ASUS | Oct 1, 2016 |
| Asus Zenfone Go ZB500KL | X00ADC | ASUS | Oct 1, 2016 |
| Asus Zenfone Go ZB500KL | ZB500KL | ASUS | Oct 1, 2016 |
| Asus Zenfone Go ZB500KL | ZB500KG | ASUS | Oct 1, 2016 |
| Asus Zenfone Live ZB501KL | A007 | ASUS | Mar 1, 2017 |
| Asus Zenfone Go T500 | Asus Zenfone Go T500 | ASUS | Apr 1, 2016 |
| Asus Zenfone Go ZB552KL | X007D | ASUS | May 1, 2017 |
| Asus Zenfone Go ZB450KL | X009DA | ASUS | Aug 1, 2016 |
252 of 252 row(s) shown.
Rows per page
Page 1 of 26
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.
