Skip to content
Fencer Vulns
medium 6.1

CVE-2021-25372 kev in the critical feed json

An improper boundary check in DSP driver prior to SMR Mar-2021 Release 1 allows out of bounds memory access.

published 2021-03-26 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-12268

cvss
6.1
version 3.1, CNA
cisa kev
Exploited
added 2023-06-29
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

An improper boundary check in DSP driver prior to SMR Mar-2021 Release 1 allows out of bounds memory access.

Patch / fix

cisa required action Apply updates per vendor instructions or discontinue use of the product if updates are unavailable

  • Samsung Mobile Samsung Mobile Devices SMR Mar-2021 Release 1

Timeline

  1. Found exploited as a 0-day (Project Zero)
  2. 0-day patched (Project Zero)
  3. Published
  4. Added to CISA KEV
  5. CISA patch deadline
  6. CISA SSVC: exploitation active

Known exploited

Added
3 y ago
Patch by
2023-07-20 (3 y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions or discontinue use of the product if updates are unavailable
Vendor, product
Samsung, Mobile Devices
CISA name
Samsung Mobile Devices Improper Boundary Check Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Found
2020-12-22
Patched
2021-03-01
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
21 mo ago

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 6.7 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • Samsung Mobile Samsung Mobile Devices

Classification

Weakness
  • CWE-703 Improper Check or Handling of Exceptional Conditions
  • CWE-787 Out-of-bounds Write

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.