Quick answers
- Is CVE-2026-33968 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33968 being exploited in the wild.
- How severe is CVE-2026-33968?
- Low severity, with a CVSS score of 2.8, published 14 September 2026.
- Which products and versions are affected?
- Samsung Exynos 2600 <UNKNOWN>; Samsung Exynos 1330 <UNKNOWN>; Samsung Exynos 1380 <UNKNOWN>; Samsung Exynos 1480 <UNKNOWN>; and 4 more.
- Is there a fix for CVE-2026-33968?
- 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-33968 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-33968?
- Check whether you run Samsung Exynos 2600, Samsung Exynos 1330, 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
A Time-of-Check Time-of-Use (TOCTOU) race condition exists in the Samsung Exynos camera driver affecting multiple processor models (1330, 1380, 1480, 2400, 1580, 2500, 2600, 1680). The vulnerability allows out-of-bounds memory access, which can be exploited by a local attacker to read or write memory beyond intended limits. The attack requires local access to the affected device and successful timing of the race condition window. Exploitation could result in information disclosure, denial of service, or potentially privilege escalation depending on memory contents.
Affected products
- Samsung Exynos 1330 <UNKNOWN>
- Samsung Exynos 1380 <UNKNOWN>
- Samsung Exynos 1480 <UNKNOWN>
- Samsung Exynos 2400 <UNKNOWN>
- Samsung Exynos 1580 <UNKNOWN>
- Samsung Exynos 2500 <UNKNOWN>
- Samsung Exynos 2600 <UNKNOWN>
- Samsung Exynos 1680 <UNKNOWN>
Timeline
- 2026-09-14: disclosed
- 2025-12-15: other: Reported date