CVE-2021-25372: Samsung Mobile Devices Improper Boundary Check
Samsung Mobile Devices · listed in the CISA catalog of actively exploited vulnerabilities since 2023-06-29.
- CVSS v3.1 (CVE record)
- 6.1
- medium
- EPSS (exploit probability, 30 days)
- 0.8%
- higher than 57.6% of all CVEs
- Added to CISA KEV
- 2023-06-29
- US federal due date 2023-07-20
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2021-25372 explained
CVE-2021-25372 is an improper boundary check in the DSP driver of Samsung Mobile Devices. It allows out-of-bounds memory access on devices without the SMR Mar-2021 Release 1 security update. CISA lists it as known to be exploited, so unpatched devices need attention.
Impact
An attacker who succeeds can fully compromise confidentiality, integrity and availability of the affected component. CISA rates the technical impact as total. Exploitation requires physical access, high privileges and high attack complexity, with no user interaction. CISA judges it not automatable, so it cannot be exploited at scale without manual steps. Attackers are known to use this vulnerability; ransomware use is unknown.
Who is affected
The CVE record lists Samsung Mobile Devices running Android Q (10.0) and R (11.0) with exynos980, exynos2100 or exynos9830 chipsets, before SMR Mar-2021 Release 1. The fix is included in SMR Mar-2021 Release 1. Devices that have that security maintenance release or a later one are not affected according to the record.
Written with AI from the data on this page and checked against it automatically.
Official description
An improper boundary check in DSP driver prior to SMR Mar-2021 Release 1 allows out of bounds memory access.
CISA required action: Apply updates per vendor instructions or discontinue use of the product if updates are unavailable
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Samsung Mobile DevicesAffectedFixed in
- ≥ Q(10.0), R(11.0) devices with exynos980, exynos2100, exynos9830, < 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: 2023-07-20 (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. - Use device management tools to find devices with Exynos chipsets that are still below that patch level.
- Discontinue use of devices that can no longer receive updates, as CISA's required action states.
- Limit physical access to devices and restrict high-privilege access on them.
- Check devices that were exposed or unpatched for 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-25372
- Is CVE-2021-25372 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-06-29, with a US federal due date of 2023-07-20. Whether it is used in ransomware campaigns is unknown.
- Which update fixes it?
- The CVE record names
SMR Mar-2021 Release 1as the fixed version. Devices with this security release or later contain the fix. - Can it be exploited remotely?
- According to the CVSS data, no. The attack vector is physical and requires high privileges and high complexity. The impact is still total if exploited.
Written with AI from the data on this page and checked against it automatically.
References
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.