Samsung Semiconductor Exynos 2600
9 CVEs affecting Samsung Semiconductor Exynos 2600. Latest disclosed: 2026-11-05. Critical: 0, High: 0.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2026-69050 | | 2026-11-05 | Out-of-bounds memory access in a device driver due to improper resource state tracking. | |
CVE-2026-69044 | | 2026-11-05 | In the Samsung GPU driver, improper reference count handling during command submission can lead to memory corruption. | |
CVE-2026-69043 | | 2026-11-05 | In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption | |
CVE-2026-69005 | | 2026-11-05 | Integer overflow in NPU driver parameter processing due to insufficient bounds checking. | |
CVE-2026-69002 | | 2026-11-05 | Incorrect authorization in Samsung framework services due to missing permission checks | |
CVE-2026-68990 | | 2026-11-05 | In the Samsung Exynos H-Arx DRM plugin, improper input validation during buffer operations can cause memory corruption, potentially leading to denial of servic… | |
CVE-2026-68984 | | 2026-11-05 | In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption. | |
CVE-2026-48183 | | 2026-11-05 | Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions | |
CVE-2026-48178 | | 2026-11-05 | Out of bound access in PPC due to race condition in global variable access |