CVE-2024-46919
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 loadOutputBuffers.
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 loadOutputBuffers function of Samsung Exynos mobile processors (9820, 9825, 980, 990, 850, 1080, 2100, and 1280) allows a stack out-of-bounds write vulnerability. This is a memory corruption flaw at the firmware level that could lead to 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Exynos processor modelCheck the device specifications or system information to determine if the device uses one of the following Exynos chips: 9820, 9825, 980, 990, 850, 1080, 2100, or 1280. On Android devices, this can often be found in Settings > About Phone > Chipset or via commands like 'cat /proc/cpuinfo' or 'getprop ro.hardware'Affected if The device contains any of the listed Exynos processor models (9820, 9825, 980, 990, 850, 1080, 2100, or 1280)
-
Check the baseband or firmware versionRetrieve the modem/baseband firmware version. On Android, use 'AT+CGMR' via a terminal app with modem diagnostics, check Settings > About Phone > Baseband version, or use 'getprop gsm.version.baseband'Affected if The firmware version is present and corresponds to an unpatched release
-
Verify the loadOutputBuffers function contextThis is a low-level firmware vulnerability in the baseband/processor firmware. There is no user-accessible config to check. The presence of the vulnerability can only be confirmed by checking if Samsung or the device manufacturer has released a security patch for this CVE.Affected if The device vendor security bulletin does not list a fix for CVE-2024-46919
-
Check vendor security patch levelOn Android devices, check Settings > About Phone > Security Patch Level or use 'getprop ro.build.version.security_patch'. Compare this date against the date when the fix for CVE-2024-46919 was released in the Android Security Bulletin.Affected if The security patch level is earlier than the month when CVE-2024-46919 was patched
If the device uses any of the affected Exynos processors (9820, 9825, 980, 990, 850, 1080, 2100, 1280) and the vendor has not issued a firmware/security patch for CVE-2024-46919, the device is vulnerable to stack out-of-bounds write via the loadOutputBuffers function.
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 dataThis hardware/firmware vulnerability requires a security patch from Samsung and downstream device manufacturers. End users should apply firmware/security updates from their device vendors as they become available.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46919 — 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-46919 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