dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2024-27379

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_subscribe_get_nl_params(), there is no input validation check on hal_req->num_intf_addr_present 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 · moderate confidence

Heap buffer overflow in Samsung Exynos mobile processors (980, 850, 1280, 1380, 1330) in the NAN (Neighbor Awareness Networking) function slsi_nan_subscribe_get_nl_params(). The function lacks input validation on hal_req->num_intf_addr_present from userspace, allowing a local attacker to trigger heap memory corruption.

MitigationApply Samsung security firmware updates for affected Exynos processors; no workarounds available for kernel-level input validation flaws.

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 processor model
    Check the device specifications or system-on-chip (SoC) information to determine if the device uses an Exynos 980, 850, 1280, 1380, or 1330 processor. This can typically be found in /proc/cpuinfo, device settings under 'About Phone', or manufacturer documentation.
    Affected if The processor is one of: Exynos 980, 850, 1280, 1380, or 1330.
  2. Determine if NAN (Neighbor Awareness Networking) is supported
    Check if the device supports NAN/Wi-Fi Aware functionality. This can be verified by checking for the 'android.permission.NEARBY_WIFI_DEVICES' permission support, or by examining Wi-Fi driver modules for NAN-related kernel parameters (such as 'slsi_nan' or similar NAN driver components).
    Affected if The device supports and includes NAN/Wi-Fi Aware functionality.
  3. Verify the firmware version
    Retrieve the baseband or Wi-Fi firmware version for the Exynos processor. On Android devices, this information is typically available under Settings > About Phone > Software Information > Baseband version, or via 'getprop' commands (e.g., 'getprop gsm.version.baseband').
    Affected if The device uses any firmware version on the affected Exynos processors (980, 850, 1280, 1380, 1330) since all versions are vulnerable.
  4. Check for NAN service subscription capability
    Verify if applications can access NAN subscription APIs on the device. This can be tested by examining whether the Wi-Fi Aware (NAN) interface is exposed to apps or by checking if the wlan driver loads NAN-related kernel modules.
    Affected if NAN functionality is exposed and can be invoked by local applications.

A user is affected if their device contains an Exynos 980, 850, 1280, 1380, or 1330 processor with NAN/Wi-Fi Aware functionality enabled, as all firmware versions of these processors contain the heap buffer overflow vulnerability in the slsi_nan_subscribe_get_nl_params() function.

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 security firmware updates for affected Exynos processors; no workarounds available for kernel-level input validation flaws.

Fix this in Exynos 980 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-27379 — 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-27379 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