Chipset
SAMSUNG LSI Exynos 850
Also known as S5E3830
Statistics
Released (est):
April 2020
4 years ago
Vulnerabilities:
152
Devices:
45
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-43122 | MEDIUM | BOOT | FIRMWARE | Jul 27, 2023 | Dec 2023 | 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-37367 | MEDIUM | CELLULAR | FIRMWARE | Apr 27, 2023 | Sep 2023 | N/A |
CVE-2023-37368 | MEDIUM | CELLULAR | FIRMWARE | Apr 27, 2023 | Sep 2023 | N/A |
CVE-2023-37377 | LOW | N/A | OS | May 25, 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 |
152 of 152 row(s) shown.
Rows per page
Page 1 of 16
Devices
Name | Code name | Manufacturer | Release Date |
---|---|---|---|
Samsung Galaxy A12 Nacho | SM-A127F/DSN | SAMSUNG | Aug 9, 2021 |
Samsung Galaxy A12 Nacho | SM-A127F/DS | SAMSUNG | Aug 12, 2021 |
Samsung Galaxy A12 Nacho | SM-A127F | SAMSUNG | Aug 12, 2021 |
Samsung Galaxy A12 Nacho | SM-A127M | SAMSUNG | Aug 9, 2021 |
Samsung Galaxy A12 Nacho | SM-A127U | SAMSUNG | Aug 9, 2021 |
Samsung Galaxy A14 | SM-A145F | SAMSUNG | Mar 27, 2023 |
Samsung Galaxy A14 | SM-A145F/DSN | SAMSUNG | Mar 27, 2023 |
Samsung Galaxy A14 | SM-A145M | SAMSUNG | Mar 27, 2023 |
Samsung Galaxy A14 | SM-A145M/DS | SAMSUNG | Mar 27, 2023 |
Samsung Galaxy A14 | SM-A145P | SAMSUNG | Mar 27, 2023 |
45 of 45 row(s) shown.
Rows per page
Page 1 of 5
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.