dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-66369

HIGH · 7.5 CVSS v3.1 Published 2026-05-05
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 MM in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, W920, W930, W1000, Modem 5123, and Modem 5300. Incorrect handling of 5G NR NAS registration accept messages 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 confidence

A vulnerability in the Mobility Management (MM) component of Samsung's baseband processors allows malformed 5G NR NAS registration accept messages to crash the modem, causing a denial of service on affected devices. The issue stems from incorrect handling of specific fields or structures in the 5G registration acceptance process.

MitigationApply Samsung firmware updates for affected processors once released; coordinate with mobile carriers for baseband firmware patches. Until then, monitor device availability and consider network-level filtering of anomalous NAS messages if feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 baseband processor manufacturer
    Check if the device uses a Samsung baseband/modem chipset. On Samsung devices, this can be found in baseband info (e.g., *#*#4636#*#* on Android, or via AT commands like AT+CGMM). Samsung baseband processors are used in many Samsung Exynos-equipped devices, though some regions use Qualcomm modems which are not affected by this specific CVE.
    Affected if The device uses a Samsung-designed baseband processor (e.g., Exynos modem series)
  2. Confirm 5G NR capability and active connection
    Verify the device supports and is connected to 5G NR. Check via phone status (*#*#4636#*#*),Settings > Connections > Mobile Networks > Network Mode, or AT command AT+CPSI? which shows the system information including RAT (Radio Access Type).
    Affected if 5G NR (5G New Radio) is enabled and the device is registered on a 5G network
  3. Monitor for modem crashes or sudden 5G disconnections
    Check system logs for modem-related crashes. On Android, review logcat (adb logcat -b radio) or kernel logs (dmesg) for entries containing 'modem', 'mm', 'nas', 'crash', or 'subsystem restart'. Also observe if the device frequently loses 5G signal or reboots the radio interface unexpectedly.
    Affected if The modem experiences repeated crashes, restarts, or 5G connection drops that coincide with receiving NAS registration accept messages
  4. Review baseband firmware version
    Retrieve the baseband firmware version via AT command AT+CGMR or through Android's build information (Settings > About Phone > Baseband version). Compare against any Samsung security bulletins for CVE-2025-66369 once released.
    Affected if The baseband version is within the affected range provided by Samsung's security advisory (when available) and the device meets criteria in steps 1-3

A device is affected if it uses a Samsung baseband processor, has 5G NR enabled, and exhibits modem crashes or 5G connection failures, particularly after receiving NAS registration accept messages from the network.

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 firmware updates for affected processors once released; coordinate with mobile carriers for baseband firmware patches. Until then, monitor device availability and consider network-level filtering of anomalous NAS messages if feasible.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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