CVE-2025-59439
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 Samsung Mobile Processor, Wearable Processor and Modem Exynos 980, 990, 850, 1080, 9110, W920, W930, W1000 and Modem 5123. Incorrect handling of NAS Registration messages leads to a Denial of Service because of Improper Handling of Exceptional Conditions.
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 confidenceVulnerability in Samsung Exynos baseband processors (mobile, wearable, and modem chipsets) where improper handling of exceptional conditions in NAS (Non-Access Stratum) Registration messages allows remote attackers to cause a Denial of Service. The issue stems from inadequate error handling when processing malformed or unexpected NAS registration requests in the modem firmware.
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 device chipset modelCheck the device specifications or system information to determine the baseband/modem processor model. For mobile phones, this is typically the Exynos chipset model (e.g., Exynos 990, Exynos 980). For wearables, check the processor model (e.g., Exynos W920, W930, W1000). On Android, you can often find this in Settings > About Phone > Baseband or through diagnostic apps.Affected if The device uses any of the following chipsets: Exynos 990, Exynos 980, Exynos 9110, Exynos 1080, Exynos W930, Exynos W920, Exynos W1000, or Modem 5123.
-
Confirm the firmware is baseband/modem firmwareThis vulnerability exists in the modem/baseband firmware, not the main application processor OS. Verify you are checking the modem firmware version, not the Android or One UI version. On most devices, the baseband version is shown in Settings > About Phone > Baseband version or *#0011# on Samsung dialer.Affected if The baseband/modem firmware version cannot be patched by the user and is tied to the chipset's firmware.
-
Check if NAS registration handling is activeNAS (Non-Access Stratum) is a protocol layer in LTE/5G modems that handles registration, mobility, and session management. This is always active on any device with cellular connectivity. There is no user-configurable setting to disable it.Affected if The device has cellular or wearable connectivity enabled - the NAS layer is inherently active for any network connection.
If the device contains any of the listed Exynos chipsets (990, 980, 9110, 1080, W930, W920, W1000, or Modem 5123) and has cellular/network functionality enabled, the device is affected since all firmware versions for these chipsets are vulnerable.
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 for affected chipsets. Since this is a processor-level baseband vulnerability, no user workarounds exist; organizations should inventory affected devices and monitor for available updates through Samsung or OEM channels.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59439 — 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-59439 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