dbcve.org
Exynos 990 FirmwareOperating system · Samsung

CVE-2025-62818

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-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
An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. An out-of-bounds write occurs due to a mismatch between the TP-UDHI and UDL values when processing an SMS TP-UD packet.

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

An out-of-bounds write vulnerability exists in Samsung Exynos mobile processors and modems when parsing SMS TP-UD packets. The vulnerability stems from a mismatch between the TP-UDHI (User Data Header Indicator) and UDL (User Data Length) values during SMS processing, allowing memory corruption that could enable remote code execution via specially crafted SMS messages.

MitigationApply Samsung security firmware updates for affected Exynos processors and modems; organizations should inventory vulnerable devices and prioritize patching those with exposure to untrusted SMS sources.

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 990 FirmwareOperating system
Affected:all versions
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 1080 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
Exynos 1480 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the device chipset model
    Check the device specifications or system information to determine the Exynos processor model (e.g., Exynos 990, Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1330, Exynos 1380, or Exynos 1480)
    Affected if The device uses any of the following chipsets: Exynos 990, 980, 850, 1080, 1280, 1330, 1380, or 1480
  2. Check the baseband/modem firmware version
    Access the device's baseband or modem firmware information through the phone's settings (Settings > About Phone > Software Information > Baseband version) or via AT commands if available
    Affected if The baseband version corresponds to the affected firmware listed (all versions of the listed Exynos chipsets)
  3. Verify SMS functionality is enabled
    Check if SMS messaging is enabled in the device settings (Settings > Messaging or Messages > Settings). This vulnerability triggers when a specially crafted SMS is received, so SMS must be active for exploitation
    Affected if SMS reception is enabled on the device (this is the default state for most devices)
  4. Confirm the cellular modem handles SMS
    Verify that SMS is routed through the cellular baseband/modem rather than over-the-top (OTT) messaging apps that use data connections. This can be checked by confirming standard SMS/MMS functionality uses the cellular network
    Affected if SMS messages are processed by the cellular baseband/modem (standard SMS behavior)

A device is affected if it uses any of the listed Exynos chipsets (990, 980, 850, 1080, 1280, 1330, 1380, 1480) with baseband firmware and has SMS functionality enabled, since all firmware versions of these chipsets are vulnerable to the TP-UDHI/UDL mismatch during SMS parsing.

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 Samsung security firmware updates for affected Exynos processors and modems; organizations should inventory vulnerable devices and prioritize patching those with exposure to untrusted SMS sources.

Fix this in Exynos 990 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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