dbcve.org
Exynos 990 FirmwareOperating system · Samsung

CVE-2025-27807

CRITICAL · 9.1 CVSS v3.1 Published 2026-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 9110, W920, W930, W1000, Modem 5123, Modem 5300, Modem 5400. The lack of a length check leads to out-of-bounds writes via malformed NAS packets.

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 buffer overflow vulnerability exists in Samsung Exynos baseband processors where NAS (Non-Access Stratum) protocol packet parsing lacks proper length validation. Attackers sending malformed NAS packets can trigger out-of-bounds memory writes, potentially achieving remote code execution in the modem context.

MitigationApply Samsung firmware/security updates for affected processors (mobile, wearable, modem) as they become available. No user-facing workarounds exist for this firmware-level vulnerability.

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 990 FirmwareOperating system
Affected:all versions
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 1080 FirmwareOperating system
Affected:all versions
Exynos 2100 FirmwareOperating system
Affected:all versions
Exynos 1280 FirmwareOperating system
Affected:all versions
Exynos 2200 FirmwareOperating system
Affected:all versions
Exynos 1330 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
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 model
    Check the device or system documentation, or query the modem/baseband subsystem (for example, via AT command AT+CGMM or through /proc/cpuinfo on Android, or check kernel boot logs for baseband chip identifier)
    Affected if The processor is one of: Exynos 990, 980, 850, 1080, 2100, 1280, 2200, or 1330
  2. Confirm cellular modem is active
    Verify that the device has an active cellular connection or that the baseband modem is powered on (check for cellular network registration, radio interface active)
    Affected if The cellular modem is powered on and processing NAS (Non-Access Stratum) protocol messages, which is the normal state for any device with cellular capability using these chipsets
  3. Check for baseband crash logs
    Review system logs (logcat, dmesg, or baseband-specific logs) for modem crashes, unexpected restarts, or memory corruption indicators that may indicate exploitation attempts
    Affected if Unexpected modem crashes, out-of-bounds memory errors, or abnormal baseband restart events are present in logs

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Samsung firmware/security updates for affected processors (mobile, wearable, modem) as they become available. No user-facing workarounds exist for this firmware-level vulnerability.

Recommended fix Moderate confidence

Samsung Security Maintenance Release (SMR) containing patch for CVE-2025-27807 - verify specific version with device/firmware vendor

  1. Check Samsung's official semiconductor security advisory at semiconductor.samsung.com for the latest firmware security bulletins
  2. Identify the specific Exynos chipset variant in your device (980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 9110, W920, W930, W1000, Modem 5123/5300/5400)
  3. Contact the device manufacturer (Samsung, or other OEMs using these chipsets) to verify if a firmware/security patch addressing CVE-2025-27807 is available
  4. Apply the manufacturer's firmware update or security patch (SMR - Samsung Maintenance Release) that includes the fix for this vulnerability
  5. For embedded/IoT devices using these chipsets, obtain the patched firmware directly from Samsung Semiconductor
Caveat Firmware updates carry risk of device malfunction; ensure backup and test in controlled environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Exynos 990 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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