# CVE-2025-54325: Race condition in n/a

> A race condition in the VTS driver of Samsung Exynos processors allows attackers to perform an out-of-bounds read, resulting in information disclosure.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-434w-5hh5-c4p5

## What is CVE-2025-54325?

CVE-2025-54325 is a medium-severity vulnerability in Samsung Exynos 1080 Firmware, published on 4 Nov 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 VTS in Samsung Mobile Processor and Wearable Processor Exynos 1080, 1280, 2200, 1380, 1480, 2400, 1580, 2500, W920, W930, W1000. A race condition in the VTS driver results in an out-of-bounds read, leading to an information leak.

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

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

It affects 11 products.


Products: Samsung Exynos 1080 Firmware, Samsung Exynos 1280 Firmware, Samsung Exynos 1380 Firmware, Samsung Exynos 1480 Firmware, Samsung Exynos 1580 Firmware, Samsung Exynos 2200 Firmware, Samsung Exynos 2400 Firmware, Samsung Exynos 2500 Firmware, Samsung Exynos W1000 Firmware, Samsung Exynos W920 Firmware, Samsung Exynos W930 Firmware.

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

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

## Is CVE-2025-54325 being exploited?

There is no known exploitation of CVE-2025-54325 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-54325 and fix it if it is affected.

What it is: CVE-2025-54325 is a medium-severity vulnerability in Samsung Exynos 1080 Firmware, published on 4 Nov 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-54325 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-54325/ (Markdown: https://insights.sbomify.com/CVE-2025-54325/index.md)
```

## Sources

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

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