# CVE-2026-33957: Memory corruption in Exynos 1580 firmware

> An out-of-bounds read and write in the CustOS Driver allows attackers to cause memory corruption or leak information on Samsung Exynos 1580 devices.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/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-4cjw-7m6g-3q48

## What is CVE-2026-33957?

CVE-2026-33957 is a medium-severity memory corruption vulnerability in Samsung Exynos 1580 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 CustOS Driver in Samsung Mobile Processor Exynos 1580. Requesting oversized shared memory from the custos_iwc device enables out-of-bounds read and write, potentially leading to memory corruption or information leakage.

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

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


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

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

## Is CVE-2026-33957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33957 is a medium-severity memory corruption vulnerability in Samsung Exynos 1580 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-33957 in the wild and no public exploit code.

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

## Sources

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

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