CVE-2024-27372
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 · uneditedAn 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 disc_attr->infrastructure_ssid_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 confidenceA missing bounds check on the `infrastructure_ssid_len` field in the NAN (Neighbor Awareness Networking) function `slsi_nan_config_get_nl_params()` allows userspace to supply an arbitrary length value. This value is used directly in memory copy operations without validation, causing a heap buffer overflow that can lead to arbitrary code execution or denial of service.
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 dataall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Exynos chipset modelCheck /proc/cpuinfo or dmesg for the processor identifier, or use 'getprop ro.hardware' on Android devices to determine the exact Exynos model numberAffected if The device uses an Exynos 980, 850, 1280, 1380, or 1330 processor
-
Check firmware versionRetrieve the firmware version string from the Wi-Fi subsystem (e.g., via 'wlan_driver' debug interface, /sys/class/wlan, or vendor-specific diagnostic tools). Compare against known fixed versions if available from Samsung security advisoriesAffected if Firmware version cannot be determined or is older than any Samsung-patched release for this CVE
-
Verify NAN feature is enabledCheck if Neighbor Awareness Networking (NAN) is active by examining wlan driver state: use 'iw list' or vendor-specific commands like 'wpa_cli -i wlan0 NAN' status. Look for NAN interface or peer entriesAffected if NAN functionality is enabled and operational on the device
-
Inspect NAN configuration parametersExamine NAN-related configuration files or debug interfaces for the infrastructure_ssid_len parameter handling. Use packet captures or firmware debug logs to observe how NAN SSID lengths are processed by the slsi_nan_config_get_nl_params functionAffected if NAN configuration allows arbitrary infrastructure_ssid_len values without validation (requires firmware-level inspection or Samsung's confirmation)
A user is affected if their device runs any of the listed Exynos firmware variants (980, 850, 1280, 1380, 1330) with NAN enabled and the infrastructure_ssid_len parameter is not properly bounds-checked by the current firmware version.
Generated from the published advisory. Verify against your own configuration.
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 dataSamsung must release firmware/microcode updates for affected Exynos processors that add proper validation of the `infrastructure_ssid_len` parameter against maximum SSID length limits before performing heap allocations or memory copies.
- Consultation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27372 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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