CVE-2024-27386
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 · uneditedA 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 tx 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 · moderate confidenceA heap buffer overflow vulnerability exists in Samsung's Exynos 1380 and 1480 modem drivers. The slsi_handle_nan_rx_event_log_ind function processes a tag_len value from userspace without validating that it stays within allocated buffer bounds, allowing a malicious userspace application to overwrite heap memory.
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 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the chipset modelCheck the device hardware specifications or use system information commands (e.g., 'cat /proc/cpuinfo' on Android, or check device model specifications) to determine if the device uses an Exynos 1380 or Exynos 1480 processorAffected if The device uses an Exynos 1380 or Exynos 1480 chipset
-
Determine modem firmware versionAccess the modem firmware information through device diagnostics, modem debug logs, or vendor-specific AT commands (e.g., AT+CGMR or ATI) if availableAffected if The modem firmware version cannot be verified as patched because no patched versions are publicly known for these chipsets
-
Check if NAN (Neighbor Awareness Networking) is enabledInspect Wi-Fi settings or wireless configuration files to determine if Wi-Fi Direct or NAN features are turned on. On Android, check via 'settings list global' or look for 'nan' or 'wifi_direct' in config filesAffected if NAN/Wi-Fi Direct is enabled and the device uses an affected Exynos chipset
-
Verify the vulnerable driver module is presentCheck for the presence of the slsi modem driver or related firmware modules in the filesystem (typically in /vendor/firmware or /lib/firmware). Use 'find' or 'ls' commands to locate files containing 'slsi' or 'nan' in the firmware directoryAffected if The slsi_handle_nan_rx_event_log_ind function exists in the loaded modem firmware and processes NAN events without bounds checking
A user is affected if their device contains an Exynos 1380 or 1480 chipset with the slsi modem driver that processes NAN events, particularly when NAN/Wi-Fi Direct features are enabled.
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 patch the slsi_handle_nan_rx_event_log_ind function to validate tag_len against buffer size before use. End users should apply vendor firmware updates as they become available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27386 — 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-27386 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