Security Resilience

CVE-2021-25395

Race Condition in Samsung Android 10.0 … 9.0

CISA KEVActive ExploitationEUVD ExploitedRace Condition
Published
11 June 2021
Modified
30 October 2025
KEV Added
29 June 2023
Patch / advisory
CVSS Score v3.1 6.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0037 29th percentile
Risk Priority 75 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2021-25395 is a medium-severity Race Condition (CWE-362) vulnerability in Samsung Android. Its CVSS base score is 6.4 (Medium).

Operationally, ranked at the 29th percentile by exploit likelihood (below the median); CISA has added it to the Known Exploited Vulnerabilities catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A race condition vulnerability, tracked as CVE-2021-25395 and assigned CWE-362, exists in the MFC charger driver on Samsung devices prior to the SMR MAY-2021 Release 1. The flaw permits local attackers to bypass signature verification checks when radio-level privileges have already been obtained, carrying a CVSS 3.1 score of 6.4 that reflects high impact on confidentiality, integrity, and availability under local attack conditions with high complexity and high privileges required.

An attacker who has first compromised radio privileges can leverage the race condition to bypass signature enforcement, potentially allowing unauthorized code execution or modification of protected charger-related components on the affected device.

Samsung's May 2021 security updates address the issue by updating the MFC charger driver, and the vulnerability is catalogued by CISA among known exploited vulnerabilities, indicating confirmed in-the-wild exploitation activity.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A race condition in MFC charger driver prior to SMR MAY-2021 Release 1 allows local attackers to bypass signature check given a radio privilege is compromised.

CWE(s)
KEV Date Added
29 June 2023

Related Threats

CVEs Like This One

CVE-2021-25394Same product: Samsung Androidboth on KEV
CVE-2023-21492Same product: Samsung Androidboth on KEV
CVE-2025-21042Same product: Samsung Androidboth on KEV
CVE-2021-25489Same product: Samsung Androidboth on KEV
CVE-2021-25487Same product: Samsung Androidboth on KEV
CVE-2021-25370Same product: Samsung Androidboth on KEV
CVE-2025-21043Same product: Samsung Androidboth on KEV
CVE-2021-25369Same product: Samsung Androidboth on KEV
CVE-2021-25337Same product: Samsung Androidboth on KEV
CVE-2025-20958Same product: Samsung Android

Affected Assets

samsung
android
10.0, 11.0, 8.1, 9.0

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-362

Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.

addresses: CWE-362

Coordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing including code scans/penetration tests, developer training) that reach race conditions in concurrent code, but only as one slice of a broad requirement whose implementation scope and rigour are left to the organisation.

blocks

A.8.26 explicitly lists resilience against malicious attacks including SQL injections and input validation as application security requirements to identify/address; race conditions are a similar class of timing-based concurrency flaw that can be mitigated by requirements for proper synchronization/locking, but this is only one slice of the broad CWE-362 class (most instances arise in low-level shared-memory or TOCTOU scenarios not named here).

blocks

Secure architecture principles require proper synchronization and resource isolation, addressing the root cause of CWE-362.

prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

finds

Security testing can detect race conditions, but does not prevent them at design or coding time.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-362, a class-level weakness, and none of its children carries one either.

References