Chipset
Qualcomm SDM439
Also known as Snapdragon 439
Statistics
Released (est):
July 2018
6 years ago
Vulnerabilities:
336
Devices:
61
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-2023-33055 | HIGH | AUDIO | OS | Mar 24, 2023 | Nov 2023 | Nov 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-2022-22076 | HIGH | TRUST | N/A | May 5, 2022 | Jun 2023 | Dec 2023 |
| CVE-2022-33264 | HIGH | CELLULAR | FIRMWARE | May 3, 2022 | Jun 2023 | Jun 2023 |
| CVE-2022-40521 | HIGH | CELLULAR | FIRMWARE | Jul 15, 2022 | Jun 2023 | Jun 2023 |
| CVE-2023-21657 | HIGH | AUDIO | OS | Nov 18, 2022 | Jun 2023 | Jun 2023 |
| CVE-2022-40504 | HIGH | CELLULAR | FIRMWARE | N/A | May 2023 | May 2023 |
| CVE-2023-21665 | HIGH | GPU | OS | Feb 8, 2023 | May 2023 | May 2023 |
336 of 336 row(s) shown.
Rows per page
Page 1 of 34
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| alcatel 3 (2019) | 5053K | ALCATEL | Jan 1, 2019 |
| alcatel 3 (2019) | 5053A | ALCATEL | Jan 1, 2019 |
| alcatel 3 (2019) | 5053Y | ALCATEL | Jan 1, 2019 |
| alcatel 3 (2019) | 5053D | ALCATEL | Jan 1, 2019 |
| alcatel 3 (2019) | 5053Y_EEA | ALCATEL | Jan 1, 2019 |
| alcatel 3 (2019) | 5053D_EEA | ALCATEL | Jan 1, 2019 |
| Samsung Galaxy M01 | SM-M015G | SAMSUNG | Jun 2, 2020 |
| Samsung Galaxy M01 | SM-M015F | SAMSUNG | Jun 2, 2020 |
| Samsung Galaxy M01 | SM-M015G/DS | SAMSUNG | Jun 2, 2020 |
| Samsung Galaxy M01 | SM-M015F/DS | SAMSUNG | Jun 2, 2020 |
61 of 61 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.
