CVE-2021-25370: Samsung Mobile Devices Memory Corruption
Samsung Mobile Devices · listed in the CISA catalog of actively exploited vulnerabilities since 2022-11-08.
- CVSS v3.1 (CVE record)
- 6.1
- medium
- EPSS (exploit probability, 30 days)
- 0.9%
- higher than 60.2% of all CVEs
- Added to CISA KEV
- 2022-11-08
- US federal due date 2022-11-29
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2021-25370 explained
CVE-2021-25370 is a memory corruption flaw in the dpu driver of Samsung Mobile Devices. An incorrect implementation for handling file descriptors leads to memory corruption and kernel panic. CISA lists it as known exploited, which makes patching affected devices a priority.
Impact
Successful exploitation corrupts kernel memory and can cause a kernel panic. The CVSS vector rates confidentiality, integrity and availability impact as high. It requires physical access, high privileges and high attack complexity, with no user interaction. CISA rates the technical impact as total but not automatable, so attacks cannot easily be run at scale. CISA's catalog confirms real-world exploitation.
Who is affected
Samsung Mobile Devices running selected O(8.X), P(9.0), Q(10.0) and R(11.0) builds before the SMR Mar-2021 Release 1 security maintenance release are affected. The record lists the range as ≥ Selected O(8.X), P(9.0), Q(10.0), R(11.0), < SMR Mar-2021 Release 1. The fix is included in SMR Mar-2021 Release 1.
Written with AI from the data on this page and checked against it automatically.
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Samsung Mobile DevicesAffectedFixed in
- ≥ Selected O(8.X), P(9.0), Q(10.0), R(11.0), < SMR Mar-2021 Release 1
- SMR Mar-2021 Release 1
| Product | Affected | Fixed in |
|---|---|---|
| Samsung Mobile Devices |
|
|
How to fix it
- Update to a fixed version: SMR Mar-2021 Release 1.
- Vendor advisory: security.samsungmobile.com/securityUpdate.smsb
- CISA's deadline for US federal agencies: 2022-11-29 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the
SMR Mar-2021 Release 1security update or a later one on all affected Samsung devices. - Follow Samsung's vendor advisory, in line with CISA's required action to apply updates per vendor instructions.
- Use mobile device management to find devices still below
SMR Mar-2021 Release 1and enforce updates. - Limit physical access to devices and restrict privileged access on them.
- Check devices that stayed unpatched for unexplained kernel panics or other signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-703 Improper Check or Handling of Exceptional Conditions
Questions about CVE-2021-25370
- Is CVE-2021-25370 exploited in the wild?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-11-08, with a US federal due date of 2022-11-29. Whether it is used in ransomware campaigns is unknown.
- Which update fixes it?
- Samsung's security maintenance release
SMR Mar-2021 Release 1contains the fix. Devices on that release or later are not affected according to the CVE record. - Can it be exploited remotely?
- The CVSS vector lists a physical attack vector with high privileges and high complexity. CISA rates it as not automatable, but the technical impact as total.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.