dbcve.org
Exynos 9810 FirmwareOperating system · Samsung

CVE-2023-37368

HIGH · 7.5 CVSS v3.1 Published 2023-09-08
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 Samsung Exynos Mobile Processor, Automotive Processor, and Modem (Exynos Mobile Processor, Automotive Processor, and Modem - Exynos 9810, Exynos 9610, Exynos 9820, Exynos 980, Exynos 850, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 9110, Exynos W920, Exynos Modem 5123, Exynos Modem 5300, and Exynos Auto T5123). In the Shannon MM Task, Missing validation of a NULL pointer can cause abnormal termination via a malformed NR MM packet.

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

This vulnerability exists in Samsung Exynos processors' Shannon MM (Mobility Management) task within baseband firmware. Missing validation of a NULL pointer when processing malformed NR (New Radio) MM packets causes abnormal termination, resulting in denial of service. The issue affects multiple mobile processors, automotive processors, and modem chipsets spanning generations.

MitigationApply Samsung firmware/security updates for affected Exynos processors and modems. Since this is a baseband-level vulnerability in chipset firmware, network-level mitigations are not applicable; device-level patching is 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 data
Exynos 9810 FirmwareOperating system
Affected:all versions
Exynos 9610 FirmwareOperating system
Affected:all versions
Exynos 9820 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 2200 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
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 Exynos processor model
    Check the device or system specification sheet, or use commands like 'cat /proc/cpuinfo' on Android devices, to determine the exact Exynos chipset model (e.g., Exynos 9810, 9820, 2100, etc.)
    Affected if The device uses any of the following: Exynos 9810, 9610, 9820, 980, 850, 1080, 2100, or 2200
  2. Check baseband firmware version
    On Android devices, dial *#1234# or go to Settings > About Phone > Software Information to view the baseband/MODEM firmware version. Alternatively, use 'AT+CGMR' command via serial debug or check /system/etc/firmware for modem blobs
    Affected if The baseband firmware version is any version (all versions of the listed chipsets are affected)
  3. Verify NR/5G capability is enabled
    Check if the device has 5G/NR network capability enabled in Settings > Mobile Networks > Network Mode, or observe if the device connects to 5G towers. The vulnerability triggers when processing malformed NR MM packets
    Affected if NR (New Radio/5G) is enabled and the device can receive 5G connections - this is the attack surface for the vulnerability
  4. Confirm baseband firmware patch status
    Contact Samsung or device manufacturer to verify if the applied baseband firmware includes the CVE-2023-37368 fix. Check Samsung security bulletins for patch month/year information
    Affected if The baseband firmware predates the Samsung security update containing the fix for this vulnerability

A user is affected if their device uses an affected Exynos chipset (9810, 9610, 9820, 980, 850, 1080, 2100, 2200) and the baseband firmware has not been patched to address the NULL pointer validation issue in the Shannon MM task when processing NR packets.

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/security updates for affected Exynos processors and modems. Since this is a baseband-level vulnerability in chipset firmware, network-level mitigations are not applicable; device-level patching is required.

Fix this in Exynos 9810 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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