Samsung Semiconductor Exynos 1680 Device Driver out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.9 | $0-$5k | 0.35+ |
Summary
A vulnerability described as very critical has been identified in Samsung Semiconductor Exynos 1480, Exynos 2400, Exynos 1580, Exynos 2500, Exynos 2600 and Exynos 1680. This vulnerability affects unknown code of the component Device Driver. Such manipulation leads to out-of-bounds. This vulnerability is traded as CVE-2026-69050. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in Samsung Semiconductor Exynos 1480, Exynos 2400, Exynos 1580, Exynos 2500, Exynos 2600 and Exynos 1680. It has been rated as very critical. Affected by this issue is an unknown code block of the component Device Driver. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Out-of-bounds memory access in a device driver due to improper resource state tracking.
The advisory is shared for download at semiconductor.samsung.com. This vulnerability is handled as CVE-2026-69050 since 08/03/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 11/05/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.9
VulDB Base Score: 9.9
VulDB Temp Score: 9.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/03/2026 CVE reserved11/05/2026 Advisory disclosed
11/05/2026 VulDB entry created
11/05/2026 VulDB entry last update
Sources
Advisory: semiconductor.samsung.comStatus: Not defined
CNA: samsungsemiconductor
CVE: CVE-2026-69050 (🔒)
GCVE (CVE): GCVE-0-2026-69050
GCVE (VulDB): GCVE-100-431324
Entry
Created: 11/05/2026 03:59Changes: 11/05/2026 03:59 (51)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.