Chipset
SAMSUNG LSI Exynos 9610
Statistics
Released (est):
October 2018
6 years ago
Vulnerabilities:
150
Devices:
13
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-41111 | HIGH | CELLULAR | FIRMWARE | Mar 31, 2023 | Nov 2023 | N/A |
| CVE-2023-41112 | HIGH | CELLULAR | FIRMWARE | Mar 31, 2023 | Nov 2023 | N/A |
| CVE-2023-37368 | MEDIUM | CELLULAR | FIRMWARE | Apr 27, 2023 | Sep 2023 | N/A |
| CVE-2023-36481 | MEDIUM | CELLULAR | FIRMWARE | Apr 12, 2023 | Aug 2023 | N/A |
| CVE-2023-37366 | MEDIUM | N/A | N/A | Apr 27, 2023 | Aug 2023 | 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 |
150 of 150 row(s) shown.
Rows per page
Page 1 of 15
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| Samsung Galaxy A50 | SM-A505F | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505FN | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505GN | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505G | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505FM | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505YN | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505W | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505X | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505U | SAMSUNG | Mar 18, 2019 |
| Samsung Galaxy A50 | SM-A505GT | SAMSUNG | Mar 18, 2019 |
13 of 13 row(s) shown.
Rows per page
Page 1 of 2
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.
