dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2025-57834

HIGH · 7.5 CVSS v3.1 Published 2026-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem (Exynos 980, 850, 990, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, 1680, 9110, W920, W930, W1000, Modem 5123, Modem 5300, Modem 5400, and Modem 5410). The absence of proper input validation leads to a Denial of Service.

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 · moderate confidence

This vulnerability exists in multiple Samsung Exynos processors (mobile, wearable, and modem variants) where improper input validation can trigger a denial of service condition. The issue affects firmware in the silicon itself rather than software running on top of these processors.

MitigationApply vendor-supplied firmware updates from Samsung for affected processors. Since this is a hardware-level vulnerability in Exynos chipsets, no workarounds or compensating controls are available at the application layer.

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 1080 FirmwareOperating system
Affected:all versions
Exynos 2100 FirmwareOperating system
Affected:all versions
Exynos 1280 FirmwareOperating system
Affected:all versions
Exynos 1330 FirmwareOperating system
Affected:all versions
Exynos 1380 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Exynos processor model
    Check device specifications or system information to determine if the device contains a Samsung Exynos chip (980, 850, 990, 1080, 2100, 1280, 1330, 1380, 1480, 2400, 1580, 2500, 1680, 9110, W920, W930, or W1000). On Android devices, this may appear in 'About Phone' or via commands like 'cat /proc/cpuinfo'.
    Affected if The device contains any of the listed Exynos processor models (980, 850, 990, 1080, 2100, 1280, 1330, 1380, 1480, 2400, 1580, 2500, 1680, 9110, W920, W930, W1000)
  2. Identify Exynos modem variant
    Check device modem information (on Android: Settings > About Phone > SIM status, or via AT commands such as 'AT+CGMM' when applicable). Look for modem model numbers 5123, 5300, 5400, or 5410.
    Affected if The device contains an Exynos modem variant 5123, 5300, 5400, or 5410
  3. Check processor firmware version
    For Exynos chips in consumer devices, check for available firmware updates in Settings > Software Update. Compare your current firmware version against Samsung's update history for the specific chip model.
    Affected if The firmware version has not received patches addressing CVE-2025-57834 (all versions are currently affected according to the provided data)
  4. Check modem firmware version
    For devices with Exynos modems, verify the modem firmware version through manufacturer updates or carrier-provided firmware. This is often integrated into the main system firmware.
    Affected if The modem firmware version has not received patches addressing CVE-2025-57834

A user is affected if their device or network equipment uses any of the listed Exynos processors (980, 850, 990, 1080, 2100, 1280, 1330, 1380, 1480, 2400, 1580, 2500, 1680, 9110, W920, W930, W1000) or modem variants (5123, 5300, 5400, 5410) and the firmware has not been updated to address this input validation 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates from Samsung for affected processors. Since this is a hardware-level vulnerability in Exynos chipsets, no workarounds or compensating controls are available at the application layer.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57834 — 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-57834 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