CVE-2024-46920
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 9820, 9825, 980, 990, 850, 1080, 2100, and 1280. Lack of a length check leads to a stack out-of-bounds write at loadInputBuffers.
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 length check in the loadInputBuffers function on Samsung Exynos mobile processors (9820, 9825, 980, 990, 850, 1080, 2100, 1280) allows an attacker to write beyond the bounds of a stack-allocated buffer, resulting in a stack-based buffer overflow that could enable 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 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 chipset modelCheck the device specifications or use system information tools (such as 'cat /proc/cpuinfo' on Android, or check the device's technical specifications page) to determine the Exynos processor model numberAffected if The chipset is one of: Exynos 9820, 9825, 980, 990, 850, 1080, 2100, or 1280
-
Confirm firmware versionCheck the baseband or modem firmware version through device settings (Settings > About Phone > Software Information > Baseband version) or via AT commands if accessibleAffected if Any firmware version is present on an affected Exynos model (all versions are vulnerable)
-
Verify the vulnerable component is accessibleDetermine if the baseband processor or modem subsystem is active and processing external inputs. This may involve monitoring network traffic or checking modem logs if you have root access or diagnostic toolsAffected if The baseband/modem subsystem is enabled and processing untrusted input data
-
Check for indicators of exploitationReview any available security logs, crash dumps, or kernel logs for signs of unexpected baseband crashes, unusual modem behavior, or evidence of stack-based buffer overflows (such as crash reports mentioning 'loadInputBuffers' or similar memory corruption patterns)Affected if Exploitation indicators are present in logs or crash dumps
The device is affected if it uses any of the listed Exynos chipsets (9820, 9825, 980, 990, 850, 1080, 2100, 1280) and the baseband/modem component processing external inputs is 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.
dbcve · scopedApply vendor-supplied firmware/security updates from Samsung for affected devices; until patches are available, monitor for exploitation attempts and minimize exposure of vulnerable devices to untrusted inputs.
- Check Samsung's official security bulletin at semiconductor.samsung.com for the specific security update addressing this vulnerability
- Contact your device manufacturer (Samsung or downstream OEM) to obtain firmware updates for the affected Exynos chipset
- Apply the vendor-supplied firmware update that includes the fix for CVE-2024-46920
- Verify the firmware version after update matches the corrected release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46920 — 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-46920 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