CVE-2024-50600
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 and Wearable Processor Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, W920, W930, and W1000. Lack of a boundary check in STOP_KEEP_ALIVE_OFFLOAD leads to out-of-bounds access. An attacker can send a malformed message to the target through the Wi-Fi driver.
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 boundary check missing in the STOP_KEEP_ALIVE_OFFLOAD function within the Wi-Fi driver of Samsung Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, W920, W930, W1000) allows out-of-bounds memory access via malformed messages sent by an attacker.
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 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Exynos processor modelCheck the device or system information to determine the exact Exynos chipset model (e.g., Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, W920, W930, or W1000). This may be found in /proc/cpuinfo, device specifications, or system BIOS/UEFI information.Affected if The device uses any of these Exynos models: 980, 850, 1080, 1280, 1330, 1380, 1480, W920, W930, or W1000
-
Check Wi-Fi firmware versionRetrieve the Wi-Fi firmware version from the affected device. On Android devices this may be accessible via settings, about phone, or diagnostic tools. On other embedded systems check the Wi-Fi module firmware information (e.g., via iw, ethtool, or vendor-specific tools).Affected if The Wi-Fi firmware version is any version on the affected Exynos models, as all versions are vulnerable
-
Verify Wi-Fi keep-alive offload featureInspect whether the Wi-Fi driver has the STOP_KEEP_ALIVE_OFFLOAD function present and is capable of being invoked. This may require checking driver logs, module information (lsmod, modinfo), or Wi-Fi stack configuration.Affected if The Wi-Fi driver includes the STOP_KEEP_ALIVE_OFFLOAD function and keep-alive offload feature is supported/enabled in the wireless stack
A device is affected if it contains any of the listed Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, W920, W930, W1000) with Wi-Fi functionality and the keep-alive offload feature is present in the firmware.
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 firmware updates when released by Samsung; until then, restrict network access to affected devices to reduce attack surface.
- Consultation8.0 h
- Testing4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50600 — 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-50600 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