Chipset
Qualcomm SM8150
Also known as Snapdragon 855
Statistics
Released (est):
January 2019
6 years ago
Vulnerabilities:
431
Devices:
184
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-33024 | MEDIUM | CELLULAR | FIRMWARE | Jan 20, 2023 | Dec 2023 | N/A |
| 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-33031 | HIGH | AUDIO | OS | Mar 21, 2023 | Nov 2023 | Nov 2023 |
| CVE-2023-33055 | HIGH | AUDIO | OS | Mar 24, 2023 | Nov 2023 | Nov 2023 |
431 of 431 row(s) shown.
Rows per page
Page 1 of 44
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| Asus ROG Phone II ZS660KL | ASUS_I001D | ASUS | Sep 1, 2019 |
| Asus ROG Phone II ZS660KL | I001DA | ASUS | Sep 1, 2019 |
| Asus ROG Phone II ZS660KL | I001DE | ASUS | Sep 1, 2019 |
| Asus ROG Phone II ZS660KL | I001DC | ASUS | Sep 1, 2019 |
| Asus ROG Phone II ZS660KL | I001DB | ASUS | Sep 1, 2019 |
| Asus ROG Phone II ZS660KL | I001D | ASUS | Sep 1, 2019 |
| Asus ROG Phone II ZS660KL | I001DD | ASUS | Sep 1, 2019 |
| Asus Zenfone 6 ZS630KL | ASUS_I01WD | ASUS | May 1, 2019 |
| Asus Zenfone 6 ZS630KL | ZS630KL | ASUS | May 1, 2019 |
| Asus Zenfone 6 ZS630KL | I01WD | ASUS | May 1, 2019 |
184 of 184 row(s) shown.
Rows per page
Page 1 of 19
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.
