# CVE-2021-25370: Samsung Mobile Devices Memory Corruption

> Incorrect file descriptor handling in the DPU driver causes memory corruption and kernel panic, requiring a security patch for Samsung mobile devices.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 8 Nov 2022 (CISA KEV)
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2021
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-hhhg-3qxh-mmh3

## What is CVE-2021-25370?

CVE-2021-25370 is a medium-severity use after free vulnerability in Samsung Android, published on 26 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An incorrect implementation handling file descriptor in dpu driver prior to SMR Mar-2021 Release 1 results in memory corruption leading to kernel panic.

Weakness: CWE-416 (Use After Free), CWE-703 (Improper Check or Handling of Exceptional Conditions)

## Which versions are affected by CVE-2021-25370?

It affects 1 product.


Products: Samsung Android.

## How do I fix CVE-2021-25370?

No fix has been published for CVE-2021-25370 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Nov 2022.

## Is CVE-2021-25370 being exploited?

Yes. Attackers have exploited CVE-2021-25370 in the wild since at least 8 Nov 2022.

## Other vulnerabilities in Samsung Android

- [CVE-2025-21042](https://insights.sbomify.com/CVE-2025-21042/): Samsung Mobile Devices Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2025-21043](https://insights.sbomify.com/CVE-2025-21043/): Samsung Mobile Devices Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2021-25487](https://insights.sbomify.com/CVE-2021-25487/): Samsung Mobile Devices Out-of-Bounds Read (high 7.3, exploited in the wild)
- [CVE-2021-25394](https://insights.sbomify.com/CVE-2021-25394/): Samsung Mobile Devices Race Condition (medium 6.4, exploited in the wild)
- [CVE-2021-25395](https://insights.sbomify.com/CVE-2021-25395/): Samsung Mobile Devices Race Condition (medium 6.4, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25370 and fix it if it is affected.

What it is: CVE-2021-25370 is a medium-severity use after free vulnerability in Samsung Android, published on 26 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-25370 in the wild since at least 8 Nov 2022.

Affected product: Samsung Android. 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-2021-25370/ (Markdown: https://insights.sbomify.com/CVE-2021-25370/index.md)
```

## Sources

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

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