dbcve.org
Exynos 9820 FirmwareOperating system · Samsung

CVE-2024-52924

HIGH · 7.5 CVSS v3.1 Published 2025-03-06
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 NRMM in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. Lack of boundary check during the decoding of Registration Accept messages can lead to out-of-bounds writes on the stack

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 the NRMM (Non-Access Stratum Message Manager) component of Samsung Exynos mobile and wearable processors. During decoding of 5G/NR Registration Accept messages, the lack of proper boundary checking allows an attacker to trigger out-of-bounds stack writes, potentially leading to code execution or denial of service.

MitigationSamsung firmware updates address this vulnerability; affected device owners should apply available security patches. Organizations with fleet deployments should coordinate with Samsung for firmware rollout.

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 9820 FirmwareOperating system
Affected:all versions
Exynos 9825 FirmwareOperating system
Affected:all versions
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos 990 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

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 Exynos chipset model
    Check the device or system-on-chip information. On Android, this is typically found in Settings > About Phone > Chipset or via commands like 'cat /proc/cpuinfo' or 'getprop ro.hardware'. For wearable devices, check the device specifications or use diagnostic tools.
    Affected if The chipset matches one of the following: Exynos 9820, 9825, 980, 990, 850, 1080, 2100, or 1280
  2. Check if 5G/NR functionality is enabled
    Verify whether the device has 5G or NR (New Radio) capability active. On mobile devices, check Settings > Mobile Networks > Network Mode or similar. On affected devices without 5G service or where 5G is explicitly disabled in airplane mode or network settings, the NRMM component may not be actively processing Registration Accept messages.
    Affected if 5G/NR capability is enabled and the device connects to 5G networks, meaning the NRMM component is actively decoding 5G/NR Registration Accept messages
  3. Verify the baseband/modem firmware version
    Retrieve the modem or baseband firmware version. On Android, use 'cat /proc/version' or 'getprop gsm.version.baseband'. For diagnostic access, AT commands like 'AT+CGMR' or 'AT+SWR' may reveal the firmware version. Compare against any available security patch information from Samsung.
    Affected if The device uses one of the affected Exynos chipsets and is running firmware that has not received the security patch for CVE-2024-52924 (note: all listed firmware versions are affected unless a subsequent security update has been applied)

A device is affected if it uses any of the listed Exynos chipsets (9820, 9825, 980, 990, 850, 1080, 2100, or 1280) and has 5G/NR functionality enabled, as the vulnerability exists in the NRMM component that processes 5G Registration Accept messages.

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

Samsung firmware updates address this vulnerability; affected device owners should apply available security patches. Organizations with fleet deployments should coordinate with Samsung for firmware rollout.

Fix this in Exynos 9820 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing20.0 h
  • Review / QA12.0 h
56.0 hours of engineering $9,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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