dbcve.org
Exynos 1080 FirmwareOperating system · Samsung

CVE-2024-27387

HIGH · 7.8 CVSS v3.1 Published 2024-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. In the function slsi_rx_range_done_ind(), there is no input validation check on rtt_id coming from userspace, which can lead to a heap overwrite.

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 heap overflow vulnerability exists in the slsi_rx_range_done_ind() function in Samsung Exynos mobile processors (980, 850, 1280, 1380, 1330). The rtt_id parameter received from userspace is not validated before use, allowing a malicious userspace application to overwrite heap memory by providing a crafted rtt_id value.

MitigationApply Samsung firmware/security updates for affected devices once released. Until then, limit exposure by restricting which applications can access relevant hardware interfaces and monitor for anomalous behavior.

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 1080 FirmwareOperating system
Affected:all versions
Exynos 1280 FirmwareOperating system
Affected:all versions
Exynos 1330 FirmwareOperating system
Affected:all versions
Exynos 1380 FirmwareOperating system
Affected:all versions
Exynos 1480 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos W920 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 processor model in your device
    Check the device specifications or use system information tools (e.g., 'cat /proc/cpuinfo' on Android, or check the device model/board documentation). Look for Exynos chip identifiers such as 980, 850, 1280, 1380, 1330, 1080, 1480, or W920.
    Affected if The device contains any of the following Exynos chips: 980, 850, 1280, 1380, 1330, 1080, 1480, or W920.
  2. Determine the firmware version of the Exynos chip
    Access the baseband/modem firmware information through device settings (Settings > About Phone > Software Information > Baseband version) or via diagnostic tools provided by the device manufacturer.
    Affected if The firmware version cannot be verified as patched, since all versions of the affected Exynos firmwares are vulnerable.
  3. Check if Wi-Fi RTT (IEEE 802.11mc) feature is enabled
    On Android devices, go to Settings > Network & Internet > Wi-Fi > Wi-Fi RTT (or look for 'RTT' or 'Fine Timing Measurement' in Wi-Fi settings). Also check if any applications have requested RTT location permissions.
    Affected if Wi-Fi RTT functionality is enabled on the device, as this triggers the vulnerable slsi_rx_range_done_ind() code path.
  4. Review application permissions for Wi-Fi RTT access
    Check which applications have location permissions that include Wi-Fi RTT capability by examining app permissions in Settings > Apps > Permissions > Location, looking for apps with RTT or 'Fine location' permissions.
    Affected if Any application has been granted Wi-Fi RTT/location permissions, providing a potential attack vector to trigger the vulnerable function.

A defender is affected if their environment contains a Samsung device with an Exynos 980, 850, 1280, 1380, 1330, 1080, 1480, or W920 processor, and Wi-Fi RTT feature is enabled or accessible to applications.

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 devices once released. Until then, limit exposure by restricting which applications can access relevant hardware interfaces and monitor for anomalous behavior.

Fix this in Exynos 1080 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-2024-27387 — 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-27387 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