How severe is CVE-2021-25370?

CVE-2021-25370 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-25370?

Affected package information for CVE-2021-25370 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2021-25370?

No fixed version has been published for CVE-2021-25370 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2021-25370 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-25370, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-25370?

CVE-2021-25370 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2021-25370 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-25370 (Samsung Mobile Devices Memory Corruption Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-11-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-11-29. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2021-25370?

CVE-2021-25370 is classified as Use After Free (CWE-416), CWE-703 (CWE-703). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2021-25370?

CVE-2021-25370 affects samsung android (5 versions, e.g. 8.0, 8.1, 9.0…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2021-25370 published, and has it been updated?

CVE-2021-25370 was published on March 26, 2021 and was last updated on January 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-11-08 — agencies required to remediate by 2022-11-29

CVE-2021-25370

MEDIUM

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

Published

Mar 26, 2021

Updated

Jan 14, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk66th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

1 product · 50 configurations

androidsamsung

5 versions

8.08.19.010.011.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An incorrect implementation handling file descriptor in dpu driver prior…

security.samsungmobile.comGoogle-sheetDec 2020

An incorrect implementation handling file descriptor in dpu driver prior…

cisa.govCISANov 2022

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2021-25370 in your stack?

O3 detects CVE-2021-25370 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works