Quick answers
- Is CVE-2026-23791 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-23791 being exploited in the wild.
- How severe is CVE-2026-23791?
- Medium severity, with a CVSS score of 4.2, published 14 September 2026.
- Which products and versions are affected?
- Samsung Exynos 2600 all; Samsung Exynos 1280 all; Samsung Exynos 1380 all; Samsung Exynos 1480 all; and 5 more.
- Is there a fix for CVE-2026-23791?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-23791 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-23791?
- Check whether you run Samsung Exynos 2600, Samsung Exynos 1280, Samsung Exynos 1380 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an out-of-bounds write in the Exynos DPU driver caused by missing input length validation during color mode Look-Up Table (LUT) parsing. The flaw allows an attacker to write beyond allocated buffer boundaries, corrupting kernel memory structures. Exploitation requires local access to invoke the vulnerable driver code path, but successful exploitation can lead to kernel memory corruption and potential privilege escalation. The issue affects multiple Exynos processor variants (1280, 2200, 1380, 1480, 2400, 1580, 2500, 1680, 2600). Patches from Samsung are expected to address this input validation gap.
Affected products
- Samsung Exynos 1280 all
- Samsung Exynos 2200 all
- Samsung Exynos 1380 all
- Samsung Exynos 1480 all
- Samsung Exynos 2400 all
- Samsung Exynos 1580 all
- Samsung Exynos 2500 all
- Samsung Exynos 1680 all
- Samsung Exynos 2600 all
Timeline
- 2026-09-14: disclosed
- 2025-12-29: advisory: Reported date per Samsung advisory