dbcve.org
Exynos 1280 FirmwareOperating system · Samsung

CVE-2025-54329

HIGH · 7.5 CVSS v3.1 Published 2025-11-04
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 NAS in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. The function used to send a multiple-payloads message (including an SMS message) lacks bounds checking, which can lead to a heap overflow.

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

A heap overflow vulnerability exists in the NAS (Non-Access Stratum) layer of Samsung's Exynos mobile processors, wearable processors, and modems. The function responsible for processing multiple-payload messages (including SMS) lacks proper bounds checking, allowing an attacker to overflow the heap buffer by sending specially crafted messages. This could enable remote code execution or denial of service on affected devices.

MitigationApply vendor-supplied firmware updates from Samsung for affected processors/modems. Until patches are available, consider network-level filtering of malformed SMS/multimedia messages as a compensating control.

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 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
Exynos 1580 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

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 the device processor model
    Check the device specifications or system information to determine if the device uses a Samsung Exynos processor (1280, 1330, 1380, 1480, 1580, 2100, 2200, or 2400). On Android, this is typically found under Settings > About Phone > SoC Name or via commands like 'cat /proc/cpuinfo'.
    Affected if The processor is any of the listed Exynos variants (1280, 1330, 1380, 1480, 1580, 2100, 2200, 2400).
  2. Check the baseband/modem firmware version
    Retrieve the modem or baseband firmware version. On Android, use 'AT+CGMR' via a terminal app with modem diagnostics, or check under Settings > About Phone > Modem Software Version. Compare this version against Samsung's published firmware releases.
    Affected if The baseband firmware version corresponds to an affected Exynos variant listed in the CVE. All firmware versions for these processors are affected.
  3. Verify SMS service is enabled
    Check if the device has SMS and multimedia messaging capability active. This is typically always enabled on mobile phones but can be verified through the Phone app settings or by checking if the device can send/receive text messages.
    Affected if SMS or multimedia messaging services are enabled on the device (this is the default state for most mobile devices).
  4. Inspect for signs of heap corruption or exploitation
    Check system logs (logcat on Android) for any unusual modem crashes, heap-related errors, or unexpected SMS processing failures. Look for patterns such as 'heap buffer overflow', 'NAS layer error', or modem restart loops.
    Affected if Unexpected modem crashes, heap corruption errors, or denial of service symptoms appear in logs, particularly after receiving SMS or multimedia messages from unknown sources.

The device is affected if it uses any of the listed Exynos processors (1280, 1330, 1380, 1480, 1580, 2100, 2200, 2400) with SMS or multimedia messaging enabled, as all firmware versions for these processors contain the 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/modems. Until patches are available, consider network-level filtering of malformed SMS/multimedia messages as a compensating control.

Fix this in Exynos 1280 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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