dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2025-47202

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In RRC in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400, the lack of a length check leads to out-of-bounds writes.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory corruption vulnerability in the Radio Resource Control (RRC) layer of Samsung's mobile/wearable modem processors. Insufficient length validation allows out-of-bounds write operations, potentially enabling arbitrary code execution or denial of service in the baseband firmware.

MitigationVendor firmware updates from Samsung are required. Organizations should identify affected devices, coordinate with Samsung and mobile carriers for patch deployment, and prioritize patching given the critical CVSS 9.1 severity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos 990 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 2100 FirmwareOperating system
Affected:all versions
Exynos 2200 FirmwareOperating system
Affected:all versions
Exynos 2400 FirmwareOperating system
Affected:all versions
Exynos 1580 FirmwareOperating system
Affected:all versions
Exynos 1080 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your device model
    Check your phone or wearable settings under 'About Phone' or 'About Device' to find the model number (e.g., SM-G980F, SM-F900, etc.)
    Affected if The device uses any Samsung Exynos chipset listed in the affected products
  2. Determine the chipset variant
    Look up your device specifications on Samsung's website or a trusted tech specification database. Confirm whether the device uses an Exynos 980, 990, 850, 2100, 2200, 2400, 1580, or 1080 processor
    Affected if The device is powered by any of the affected Exynos chipsets (980, 990, 850, 2100, 2200, 2400, 1580, 1080)
  3. Check baseband firmware version
    On Android, go to Settings > About Phone > Software Information and look for the 'Baseband' or 'Modem' version field. On wearables, check under Settings > About Watch > Software Info
    Affected if The baseband version cannot be easily determined by end users; all firmware versions for these chipsets are affected since vendor states 'all versions'
  4. Verify RRC layer is active
    The RRC (Radio Resource Control) layer is a fundamental component of cellular communication and is always active when the device has cellular or LTE/5G connectivity. No manual enablement required - this is default behavior for any phone or cellular-enabled wearable
    Affected if The device has cellular connectivity (LTE, 4G, or 5G) enabled and is powered on

If your Samsung phone or wearable uses any of the Exynos 980, 990, 850, 2100, 2200, 2400, 1580, or 1080 chipsets and has cellular connectivity, you are affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Vendor firmware updates from Samsung are required. Organizations should identify affected devices, coordinate with Samsung and mobile carriers for patch deployment, and prioritize patching given the critical CVSS 9.1 severity.

Recommended fix Moderate confidence
  1. Check for and apply the latest Samsung Android security patch update for your device, as firmware vulnerabilities in Exynos processors are addressed through monthly security updates
  2. Verify your device has the most recent firmware from Samsung's update channel
  3. If your device model is listed as affected and no update is available, monitor Samsung's security advisory pages for future patches
Caveat Firmware fixes for processor-level vulnerabilities typically delivered via Android security patch updates rather than traditional version upgrades

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,960
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47202 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data