CVE-2024-27375
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_followup_get_nl_params(), there is no input validation check on hal_req->sdea_service_specific_info_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 confidenceMissing input validation on the sdea_service_specific_info_len parameter in the slsi_nan_followup_get_nl_params() function allows userspace to supply an arbitrary length value, which is used directly in memory operations without bounds checking, leading to a heap buffer overflow in the NAN (Neighbor Awareness Networking) driver for Samsung Exynos mobile processors.
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 device processor modelCheck the system-on-chip (SoC) or processor information via /proc/cpuinfo, device settings 'About Phone' section, or using 'getprop ro.hardware' or 'cat /sys/class/socinfo/soc_id' on Android devicesAffected if The processor is a Samsung Exynos 980, 850, 1280, 1380, or 1330
-
Confirm firmware versionCheck the firmware/baseband version through Android settings under 'About Phone' > 'Software information' or via 'getprop ro.build.version.security_patch' and 'getprop ro.build.id' commandsAffected if The device runs any firmware version on the affected Exynos models (all versions are affected)
-
Verify NAN (Neighbor Awareness Networking) capabilityCheck if the NAN/Wi-Fi Aware feature is present and enabled on the device - look for 'WIFI_AWARE' in /proc/config.gz, check via 'iw list' command output, or verify in Android settings under Wi-Fi > Wi-Fi AwareAffected if The NAN feature is supported and enabled on the device (the vulnerability exists in the NAN driver)
A device is affected if it uses a Samsung Exynos 980, 850, 1280, 1380, or 1330 processor with any firmware version and has the NAN (Neighbor Awareness Networking) feature available or 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 dataApply vendor-supplied firmware/security updates from Samsung for affected Exynos processors (980, 850, 1280, 1380, 1330). This is a firmware-level vulnerability that cannot be mitigated through configuration changes.
- Consultation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27375 — 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-27375 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