# CVE-2026-23788: Memory corruption in Exynos 1280 firmware

> A heap overflow in the Exynos DRM HDR driver allows attackers to cause kernel memory corruption and system crashes on affected Samsung mobile processors.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-3hr9-ggc9-95w7

## What is CVE-2026-23788?

CVE-2026-23788 is a medium-severity memory corruption vulnerability in Samsung Exynos 1280 firmware, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in DPU in Samsung Mobile Processor Exynos 1280, 2200, and 1380. A heap overflow in the Exynos DRM HDR driver (due to improper buffer size validation) leads to kernel memory corruption and a system crash.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

No fix has been published for CVE-2026-23788 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-23788 being exploited?

There is no known exploitation of CVE-2026-23788 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23788 and fix it if it is affected.

What it is: CVE-2026-23788 is a medium-severity memory corruption vulnerability in Samsung Exynos 1280 firmware, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23788 in the wild and no public exploit code.

Affected product: Samsung Exynos 1280 firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23788/ (Markdown: https://insights.sbomify.com/CVE-2026-23788/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23788
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23788
- OSV: https://osv.dev/vulnerability/CVE-2026-23788

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23788/
Summaries are generated and may contain mistakes; the official description above is the record.