Threats / Samsung / CVE-2021-25394
CVE-2021-25394
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Samsung Mobile Devices vulnerability
Samsung mobile devices contain a use-after-free vulnerability in the MFC charger driver triggered by a race condition. Exploitation requires prior radio privilege compromise and enables arbitrary memory writes.
Verdict
Today item — known-exploited.
A race condition in Samsung's MFC charger driver creates a use-after-free condition exploitable by attackers with radio-layer access, permitting memory corruption and potential privilege escalation or code execution on affected mobile devices.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-06-29).
Probability (EPSS)
EPSS 0.00422 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Samsung, Mobile Devices. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I compromise the radio baseband processor or modem firmware to gain radio privilege on the target device.
Business
The device's cellular and wireless communications layer becomes a foothold for further system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger a race condition in the MFC charger driver by timing concurrent operations to cause a use-after-free condition.
Business
Memory safety controls are bypassed, exposing the kernel to corruption and control-flow hijacking.
3
Lateral reach — past segmentation narrative 3
Attacker
I write to freed memory regions to corrupt kernel data structures or inject executable code.
Business
The attacker gains kernel-level code execution, enabling full device compromise, data exfiltration, and persistent malware installation.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by Samsung MobileCNA
Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.