Samsung Semiconductor Exynos 1680 Exynos NPU integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.70+ |
Summary
A vulnerability identified as very critical has been detected in Samsung Semiconductor Exynos 2100, Exynos 1280, Exynos 2200, Exynos 1380, Exynos 1480, Exynos 2400, Exynos 1580, Exynos 2500, Exynos 2600 and Exynos 1680. Affected by this vulnerability is an unknown functionality of the component Exynos NPU. The manipulation leads to integer overflow. This vulnerability is documented as CVE-2026-68984. The attack needs to be performed locally. There is not any exploit available.
Details
A vulnerability was found in Samsung Semiconductor Exynos 2100, Exynos 1280, Exynos 2200, Exynos 1380, Exynos 1480, Exynos 2400, Exynos 1580, Exynos 2500, Exynos 2600 and Exynos 1680 and classified as very critical. This issue affects some unknown functionality of the component Exynos NPU. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption.
The advisory is shared at semiconductor.samsung.com. The identification of this vulnerability is CVE-2026-68984 since 08/03/2026. The exploitation is known to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
- Exynos 1280
- Exynos 1380
- Exynos 1480
- Exynos 1580
- Exynos 1680
- Exynos 2100
- Exynos 2200
- Exynos 2400
- Exynos 2500
- Exynos 2600
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.2
VulDB Base Score: 8.2
VulDB Temp Score: 8.2
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: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
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-68984 (🔒)
GCVE (CVE): GCVE-0-2026-68984
GCVE (VulDB): GCVE-100-431321
Entry
Created: 11/05/2026 03:58Changes: 11/05/2026 03:58 (51)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.