dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2024-27370

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_config_get_nl_params(), there is no input validation check on hal_req->num_config_discovery_attr 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

Missing input validation on `hal_req->num_config_discovery_attr` in the Samsung SLSi NAN (Neighbor Awareness Networking) driver allows a userspace attacker to supply an arbitrarily large value, bypassing bounds checks and triggering a heap buffer overflow. This can lead to heap memory corruption, potentially enabling privilege escalation or denial of service.

MitigationAdd proper input validation and bounds checking on `num_config_discovery_attr` before using it in memory copy operations. Validate that the value does not exceed expected maximums and aligns with allocated buffer sizes.

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 system-on-chip (SoC) model of the device. On Android, this is typically found in Settings > About Phone > Chipset or via 'cat /proc/cpuinfo' looking for 'Hardware' or 'model name'. On Linux, use 'lscpu' or check /sys/devices/system/cpu/
    Affected if The chipset is one of: Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, or Exynos 1330 (all versions are affected)
  2. Verify NAN (Neighbor Awareness Networking) driver presence
    Check if the NAN kernel module or driver is loaded. On Linux, run 'lsmod | grep -i nan' or check for 'nan' entries in /proc/modules. On Android, check /sys/module/ for NAN-related modules.
    Affected if The NAN driver module exists on the system, indicating the vulnerable code path could be reached
  3. Confirm NAN functionality is enabled
    Check if NAN is actively enabled. On Android, examine wireless settings or use 'wpa_cli' to check for NAN interface status. On Linux, run 'iw list' and look for 'NAN' under supported interface types, or check 'ip link' for 'nan0' or similar NAN interfaces.
    Affected if A NAN interface (such as nan0) exists or NAN is listed as an active capability, meaning the vulnerable code in hal_req->num_config_discovery_attr is in use
  4. Check for NAN discovery attribute configuration
    Examine NAN protocol handling. If you have access to debug logs or wpa_supplicant logs with NAN debugging enabled, look for 'Config Discovery Attr' or 'num_config_discovery_attr' in the logs. This indicates the vulnerable code path is being exercised.
    Affected if NAN discovery attributes are being processed, meaning the unchecked num_config_discovery_attr value could be passed to memory operations
  5. Review firmware version if accessible
    If you can access the firmware image or kernel driver binaries, check the version string or build information for the SLSi NAN driver. Compare against any available Samsung firmware release notes.
    Affected if The firmware/driver corresponds to any version of the affected Exynos chipsets (980, 850, 1280, 1380, 1330), as all versions are vulnerable

A defender is affected if their device uses an Exynos 980, 850, 1280, 1380, or 1330 chipset and has the NAN (Neighbor Awareness Networking) feature enabled, as the vulnerability exists in all firmware versions of these chipsets.

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

Add proper input validation and bounds checking on `num_config_discovery_attr` before using it in memory copy operations. Validate that the value does not exceed expected maximums and aligns with allocated buffer sizes.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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