CVE-2025-54328
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 · uneditedAn issue was discovered in SMS 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. A Stack-based Buffer Overflow occurs while parsing SMS RP-DATA messages.
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 confidenceA stack-based buffer overflow vulnerability exists in SMS parsing logic for RP-DATA messages across multiple Samsung Exynos mobile processors, wearable processors, and modem chips. The vulnerability allows overflow of a stack-allocated buffer during SMS message parsing, potentially enabling remote code execution or denial of service with no user interaction required.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the processor modelCheck the device specifications or use system commands (e.g., 'cat /proc/cpuinfo', 'getprop ro.hardware', or AT commands like 'ATI' on modems) to determine the Exynos processor variantAffected if The processor is one of: Exynos 980, 990, 850, 1080, 2100, 1280, 1330, or 1380
-
Confirm firmware versionRetrieve the firmware or baseband version via device settings, system logs, or AT commands (e.g., 'AT+CGMR' for modems)Affected if All firmware versions of the listed Exynos processors are affected - any version confirms exposure
-
Check if SMS functionality is enabledVerify SMS/MMS services are active on the device or modem - check device settings under 'Messages' or use AT commands such as 'AT+CPMS?' to query SMS service availabilityAffected if SMS is enabled and the device processes incoming messages, making the RP-DATA parsing vulnerable
-
Verify SMS RP-DATA message handlingInspect modem or baseband logs for RP-DATA message processing capability - this is typically a built-in feature of the cellular modem and cannot be disabled separatelyAffected if The modem handles SMS RP-DATA messages, which is standard for any device with cellular messaging capability
The environment is affected if the device or modem uses any of the listed Exynos processors (980, 990, 850, 1080, 2100, 1280, 1330, 1380) and has SMS messaging functionality enabled, as all firmware versions of these processors contain the vulnerable SMS RP-DATA parsing component.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied firmware updates from Samsung for affected devices; until patches are available, consider network-level SMS filtering as a temporary mitigation.
- Consultation12.0 h
- Implementation40.0 h
- Testing50.0 h
- Review / QA20.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $33,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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