dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2024-27377

HIGH · 7.8 CVSS v3.1 Published 2024-06-05
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_nan_get_security_info_nl(), there is no input validation check on sec_info->key_info.body.pmk_info.pmk_len 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

In the slsi_nan_get_security_info_nl() function used by Samsung's NAN (Neighbor Awareness Networking) service, the pmk_len field from userspace is used without validation to determine memory copy sizes, allowing a malicious userspace application to overwrite heap memory by providing an oversized pmk_len value.

MitigationApply Samsung firmware/security updates for affected Exynos processors (980, 850, 1280, 1380, 1330) once released. Samsung must add bounds validation on pmk_len before using it in memory operations.

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 980 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 1280 FirmwareOperating system
Affected:all versions
Exynos 1380 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
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 chipset model
    Check the device or system's processor/model information. For Samsung devices, this can be found in /proc/cpuinfo, system settings, or device specifications. Look for model numbers: Exynos 980, 850, 1280, 1380, or 1330.
    Affected if The device uses any of the following chipsets: Exynos 980, 850, 1280, 1380, or 1330 - all versions of these are affected.
  2. Determine the firmware version
    Access the firmware version of the Exynos chipset. On Samsung devices, this is typically found in Settings > About Phone > Software Information, or via diagnostic tools. Check for any available firmware version strings or build numbers.
    Affected if The firmware version is older than any Samsung security update that addresses CVE-2024-27377. Since all versions are listed as affected, any unpatched firmware version is vulnerable.
  3. Check if NAN (Neighbor Awareness Networking) service is active
    Inspect running services or network configurations to determine if the NAN feature is enabled. On Android devices, check for 'NAN' or 'Wi-Fi Aware' in settings or via diagnostic commands (e.g., 'dumpsys wifi' or 'settings list global' for wifi_aware_enabled).
    Affected if The NAN/Wi-Fi Aware feature is enabled on the device. The vulnerability exists in the slsi_nan_get_security_info_nl() function which processes NAN security information.
  4. Verify the slsi_nan driver or service presence
    Check for the presence of the slsi_nan kernel module or service. On Android/Linux systems, look for slsi_nan in /proc/modules, lsmod output, or check for related processes/services handling NAN protocol.
    Affected if The slsi_nan driver/service is present and running. This is the component containing the vulnerable function slsi_nan_get_security_info_nl().

A device is affected if it uses an Exynos 980, 850, 1280, 1380, or 1330 chipset with NAN/Wi-Fi Aware enabled and has not received the Samsung security patch for CVE-2024-27377.

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 (980, 850, 1280, 1380, 1330) once released. Samsung must add bounds validation on pmk_len before using it in memory operations.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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