CVE-2025-54324
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 NAS 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. Incorrect Handling of a DL NAS Transport packet 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 · high confidenceA vulnerability in the NAS (Non-Access Stratum) protocol layer of Samsung's baseband processors allows a specially crafted downlink NAS Transport packet to crash or hang the modem, causing complete loss of cellular connectivity (Denial of Service). The issue affects 20 different Exynos chipset variants used across mobile phones, wearables, and modems.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the cellular modem or processor modelCheck device specifications or system information to determine the exact Exynos chip or modem model. On Android devices, this may be visible in 'About Phone' > 'Model', or through processor info apps. For standalone modems, consult hardware documentation.Affected if The identified chip model matches Exynos 990, 980, 850, 1080, 1280, 1330, 1380, 1480, or modem chips 5123, 5300, or 5400
-
Verify cellular connectivity is enabledConfirm the device has cellular network capability and is connected to a mobile network. The vulnerability is triggered by specially crafted downlink NAS Transport packets received over the cellular connection.Affected if Cellular service is active and the device is connected to a carrier network
-
Check for firmware update availabilityCheck system settings for pending modem or system firmware updates. Navigate to Settings > System Update (or similar) on the affected device to see if updates have been released.Affected if Updates are available but have not been applied, indicating the device is running an unpatched firmware version (though all versions are affected)
-
Confirm vulnerability trigger conditionThe flaw is triggered specifically by downlink NAS Transport packets. A device is only vulnerable when actively connected to a cellular network where a malicious actor could inject specially crafted packets.Affected if The device is actively using cellular connectivity and cannot filter or inspect inbound NAS Transport messages at the network infrastructure level
A device is affected if it contains an Exynos 990, 980, 850, 1080, 1280, 1330, 1380, or 1480 processor or an Exynos 5123, 5300, or 5400 modem chipset and has cellular connectivity enabled, since all firmware versions of these chips are vulnerable to malformed DL NAS Transport packet handling.
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/security patches from Samsung and relevant device OEMs. Network-side filtering of malformed NAS messages may provide interim protection but is not a complete fix.
- Consultation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-54324 — 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-54324 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