# CVE-2026-23793: Memory corruption in Exynos 1330 firmware

> Out-of-bounds memory access in the camera GDC driver allows kernel memory corruption, potentially enabling code execution or privilege escalation on affected devices.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-5rq5-m79p-rmhg

## What is CVE-2026-23793?

CVE-2026-23793 is a low-severity memory corruption vulnerability in Samsung Exynos 1330 firmware, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Samsung Mobile Processor Exynos 1330, 1380, 1480, and 2400. An out-of-bounds memory access vulnerability in the camera GDC driver may lead to kernel memory corruption under certain conditions.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-23793 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23793 is a low-severity memory corruption vulnerability in Samsung Exynos 1330 firmware, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23793 in the wild and no public exploit code.

Affected product: Samsung Exynos 1330 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-23793/ (Markdown: https://insights.sbomify.com/CVE-2026-23793/index.md)
```

## Sources

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

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