CVE-2026-69043 json
In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption
published 7d ago modified yesterday also EUVD-2026-117280
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption
Patch / fix
- Samsung Semiconductor Exynos 2200 October 2026
- Samsung Semiconductor Exynos 1480 October 2026
- Samsung Semiconductor Exynos 2400 October 2026
- Samsung Semiconductor Exynos 1580 October 2026
- Samsung Semiconductor Exynos 2500 October 2026
- Samsung Semiconductor Exynos 2600 October 2026
- Samsung Semiconductor Exynos 1680 October 2026
Is CVE-2026-69043 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
Affected products
- Samsung Semiconductor Exynos 2200
- Samsung Semiconductor Exynos 1480
- Samsung Semiconductor Exynos 2400
- Samsung Semiconductor Exynos 1580
- Samsung Semiconductor Exynos 2500
- Samsung Semiconductor Exynos 2600
- Samsung Semiconductor Exynos 1680
Classification
- Weakness
-
- CWE-416 Use After Free
References
Sources
- CVE List CVE-2026-69043
- NVD CVE-2026-69043
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.