Chipset
SAMSUNG LSI Exynos 7870
Statistics
Released (est):
January 2016
9 years ago
Vulnerabilities:
144
Devices:
68
Vulnerabilities
| Id | Severity | Component | Affects | Reported on | Published by manufacturer | Published by AOSP |
|---|---|---|---|---|---|---|
| CVE-2024-20873 | MEDIUM | N/A | OS | Nov 28, 2023 | Jun 2024 | N/A |
| CVE-2023-30648 | MEDIUM | N/A | N/A | Apr 1, 2023 | Jul 2023 | N/A |
| CVE-2023-30649 | HIGH | N/A | N/A | Apr 1, 2023 | Jul 2023 | N/A |
| CVE-2023-21517 | HIGH | CELLULAR | FIRMWARE | Dec 4, 2022 | Jun 2023 | N/A |
| CVE-2023-21494 | HIGH | CELLULAR | FIRMWARE | Dec 26, 2022 | May 2023 | N/A |
| CVE-2023-21503 | HIGH | CELLULAR | FIRMWARE | Dec 23, 2022 | May 2023 | N/A |
| CVE-2023-21504 | HIGH | CELLULAR | FIRMWARE | Dec 25, 2022 | May 2023 | N/A |
| CVE-2023-21467 | MEDIUM | CELLULAR | FIRMWARE | Nov 23, 2022 | Apr 2023 | N/A |
| CVE-2023-21472 | HIGH | BOOT | FIRMWARE | Dec 21, 2022 | Apr 2023 | N/A |
| CVE-2023-21473 | HIGH | BOOT | FIRMWARE | Dec 21, 2022 | Apr 2023 | N/A |
144 of 144 row(s) shown.
Rows per page
Page 1 of 15
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| Samsung Galaxy A2 Core | SM-A260F | SAMSUNG | Apr 1, 2019 |
| Samsung Galaxy A2 Core | SM-A260G | SAMSUNG | Apr 1, 2019 |
| Samsung Galaxy M10 | SM-M105F | SAMSUNG | Feb 1, 2019 |
| Samsung Galaxy M10 | SM-M105G | SAMSUNG | Feb 1, 2019 |
| Samsung Galaxy M10 | SM-M105Y | SAMSUNG | Feb 1, 2019 |
| Samsung Galaxy M10 | SM-M105M | SAMSUNG | Feb 1, 2019 |
| Samsung Galaxy Tab Advanced2 | SM-T583 | SAMSUNG | Dec 1, 2018 |
| Samsung Galaxy On6 | SM-J600GF | SAMSUNG | May 1, 2018 |
| Samsung Galaxy J7 (2018) | SM-J737F | SAMSUNG | Jul 1, 2018 |
| Samsung Galaxy J7 (2018) | SM-J737V | SAMSUNG | Jul 1, 2018 |
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.
