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

> A race condition in the HTS driver of Samsung Exynos processors allows attackers to cause a denial of service via an out-of-bounds write.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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-v9vj-4829-7862

## What is CVE-2025-52513?

CVE-2025-52513 is a high-severity vulnerability in Samsung Exynos 2400 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 Samsung Mobile Processor Exynos 2400, 1580, 2500. A race condition in the HTS driver results in an out-of-bounds write, leading to a denial of service.

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

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

It affects 3 products.


Products: Samsung Exynos 1580 Firmware, Samsung Exynos 2400 Firmware, Samsung Exynos 2500 Firmware.

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

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

## Is CVE-2025-52513 being exploited?

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

## Other vulnerabilities in Samsung Exynos 2400 Firmware

- [CVE-2025-52512](https://insights.sbomify.com/CVE-2025-52512/): Race condition in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52513 is a high-severity vulnerability in Samsung Exynos 2400 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-52513 in the wild and no public exploit code.

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

## Sources

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

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