dbcve.org
Exynos 1380 FirmwareOperating system · Samsung

CVE-2024-27385

MEDIUM · 6.7 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability was discovered in the slsi_handle_nan_rx_event_log_ind function in Samsung Mobile Processor Exynos 1380 and Exynos 1480 related to no input validation check on tag_len for rx coming from userspace, which can lead to 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

Heap buffer overflow vulnerability in Samsung Exynos 1380 and 1480 mobile processors. The slsi_handle_nan_rx_event_log_ind function lacks validation on the tag_len field from userspace input before using it in memory operations, allowing a malicious userspace application to perform heap overwrite.

MitigationApply vendor-supplied firmware/security updates from Samsung for affected devices. Until patch is available, limit exposure by restricting untrusted application access and monitoring for anomalous device 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 1380 FirmwareOperating system
Affected:all versions
Exynos 1480 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 device chipset model
    Check the processor/SoC model on the device through system settings, /proc/cpuinfo, or manufacturer specifications. Look for 'Exynos 1380' or 'Exynos 1480' in the chipset information.
    Affected if The device uses a Samsung Exynos 1380 or 1480 processor - these are the only affected models.
  2. Check the Wi-Fi firmware version
    Query the Wi-Fi or connectivity firmware version through manufacturer diagnostic tools, firmware logs, or (*#9900#) or similar service menus on Samsung devices. The affected component is the SLSI (Samsung LSI) Wi-Fi firmware handling NAN events.
    Affected if The device runs any firmware version on Exynos 1380 or 1480 - all versions are affected according to the advisory.
  3. Determine if NAN/Wi-Fi Aware feature is enabled
    Check the device's Wi-Fi settings and active connections for NAN (Neighbor Awareness Networking) or Wi-Fi Aware functionality. This feature is used for peer-to-peer discovery. Inspect system logs for NAN-related events or the slsi_handle_nan_rx_event_log_ind function activity.
    Affected if The NAN feature is actively enabled or has been used, as the vulnerability triggers when processing NAN RX event log indications from userspace.
  4. Inspect userspace to kernel communication for NAN events
    Review any available security logs, SELinux audits, or kernel logs for suspicious NAN event indications with unusual tag_len values. The vulnerability exploits missing validation on tag_len in the slsi_handle_nan_rx_event_log_ind function.
    Affected if Unusual or malformed NAN event log indications appear in logs, indicating potential exploitation attempts.

If the device contains an Exynos 1380 or 1480 chipset and has NAN/Wi-Fi Aware functionality, the device is affected by this heap buffer overflow vulnerability until Samsung releases a firmware patch.

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 vendor-supplied firmware/security updates from Samsung for affected devices. Until patch is available, limit exposure by restricting untrusted application access and monitoring for anomalous device behavior.

Fix this in Exynos 1380 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-27385 — 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-27385 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