Skip to content
Fencer Vulns
medium 6.1

CVE-2021-25370 kev in the critical feed json

An incorrect implementation handling file descriptor in dpu driver prior to SMR Mar-2021 Release 1 results in memory corruption leading to…

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

cvss
6.1
version 3.1, CNA
cisa kev
Exploited
added 2022-11-08
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

An incorrect implementation handling file descriptor in dpu driver prior to SMR Mar-2021 Release 1 results in memory corruption leading to kernel panic.

Patch / fix

cisa required action Apply updates per vendor instructions.

  • 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
4 y ago
Patch by
2022-11-29 (3 y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Samsung, Mobile Devices
CISA name
Samsung Mobile Devices Memory Corruption 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-10
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.89% chance of exploitation in the next 30 days, higher than 59% 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 4.4 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:N/I:N/A:C

Affected products

  • Samsung Mobile Samsung Mobile Devices

Classification

Weakness
  • CWE-703 Improper Check or Handling of Exceptional Conditions
  • CWE-416 Use After Free

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.