# CVE-2025-32100: Memory corruption in n/a

> Out-of-bounds write in Exynos processors allows attackers to execute arbitrary code or escalate privileges via malformed ROHC packets.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-r9m5-532j-wc5r

## What is CVE-2025-32100?

CVE-2025-32100 is a medium-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. A programming mistake for buffer copy leads to out-of-bounds writes via malformed ROHC packets.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-32100?

It affects 19 products.


Products: Samsung Exynos 1080 Firmware, Samsung Exynos 1280 Firmware, Samsung Exynos 1330 Firmware, Samsung Exynos 1380 Firmware, Samsung Exynos 1480 Firmware, Samsung Exynos 1580 Firmware, Samsung Exynos 2100 Firmware, Samsung Exynos 2200 Firmware, Samsung Exynos 2400 Firmware, Samsung Exynos 850 Firmware, Samsung Exynos 9110 Firmware, Samsung Exynos 980 Firmware, Samsung Exynos 990 Firmware, Samsung Exynos W1000 Firmware, Samsung Exynos W920 Firmware, Samsung Exynos W930 Firmware, Samsung Modem 5123 Firmware, Samsung Modem 5300 Firmware, Samsung Modem 5400 Firmware.

## How do I fix CVE-2025-32100?

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

## Is CVE-2025-32100 being exploited?

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

## Other vulnerabilities in Samsung Exynos 1080 Firmware

- [CVE-2025-54328](https://insights.sbomify.com/CVE-2025-54328/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-62818](https://insights.sbomify.com/CVE-2025-62818/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-58349](https://insights.sbomify.com/CVE-2025-58349/): Denial of service in n/a (critical 9.1)
- [CVE-2025-27807](https://insights.sbomify.com/CVE-2025-27807/): Memory corruption in n/a (critical 9.1)
- [CVE-2025-47202](https://insights.sbomify.com/CVE-2025-47202/): Memory corruption in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32100 and fix it if it is affected.

What it is: CVE-2025-32100 is a medium-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32100 in the wild and no public exploit code.

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

## Sources

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

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