CVE-2021-25371

A vulnerability in DSP driver prior to SMR Mar-2021 Release 1 allows attackers load arbitrary ELF libraries inside DSP.

CVSS: 6.1Mediumscored by the publisher (CNA)
Exploited in the wild: Yes, in CISA KEV since 29 Jun 2023CISA deadline for US federal agencies: 20 Jul 2023
EPSS: 0.80%chance of exploitation in the next 30 daystop 43% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 26 Mar 2021analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions or discontinue use of the product if updates are unavailable (CISA's required action for this KEV entry)

Summary

Triage

Exploitable: Configuration or build time
Attack vector: physical
Weakness: CWE-912 Common Weakness
Can a WAF block it?: No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Product	Affected versions	Vendor says fixed in
Samsung Mobile Samsung Mobile Devices	>= Q(10.0), R(11.0) devices with exynos980, exynos2100, exynos9830 and < SMR Mar-2021 Release 1Vendor says fixed in: not stated	Not stated by the vendor

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

samsung:android

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs physical access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 29 Jun 2023.
CISA due date: 20 Jul 2023, the remediation deadline for US federal agencies
CISA required action: Apply updates per vendor instructions or discontinue use of the product if updates are unavailable
Public exploit code: None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC: exploitation active, automatable no, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

26 Mar 2021Published
29 Jun 2023Added to CISA KEV (exploited in the wild)824 days (about 2 years) later
20 Jul 2023CISA remediation due date (US federal agencies)21 days later
4 Feb 2025CISA SSVC assessment: exploitation active566 days (about 2 years) later
21 Oct 2025CVE record last updated259 days (about 9 months) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Metric	Value	What it means
Attack vector	PhysicalRequires physical contact with the hardware.	Requires physical contact with the hardware.
Attack complexity	HighNeeds specific conditions, a race or a particular configuration.	Needs specific conditions, a race or a particular configuration.
Privileges required	HighThe attacker needs admin-level privileges.	The attacker needs admin-level privileges.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2021-25371 being exploited?

Yes. CVE-2021-25371 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2021-25371?

CVE-2021-25371 is rated Medium with a CVSS score of 6.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2021-25371?

Yes. A fix has been recorded for CVE-2021-25371. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2021-25371 affect?

CVE-2021-25371 affects samsung:android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

3 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.