CVE-2024-39890
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, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920, W930, W1000, Modem 5123, Modem 5300. The baseband software does not properly check the length specified by the CC (Call Control). This can lead to an Out-of-Bounds write.
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 confidenceThis vulnerability exists in Samsung's baseband software across multiple Exynos processors and modems. The Call Control (CC) length field is not properly validated before use, allowing an attacker-controlled length value to trigger an out-of-bounds memory write. This is a memory corruption vulnerability in the cellular baseband processor, which handles phone calls and cellular data communications.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 Exynos chipset modelCheck the device specifications or system information to determine if the device uses a Samsung Exynos processor or modem. On Android devices, this can often be found in Settings > About Phone > Model, or by checking /proc/cpuinfo for the chipset identifier.Affected if The device contains any of these Exynos components: Modem 5123, Modem 5300, Exynos 9820, 9825, 980, 990, 850, or 1080.
-
Check baseband firmware versionAccess the baseband or modem firmware version through device diagnostics or by dialing *#1234# (on some Samsung devices) which displays the firmware version, or through Settings > About Phone > Software Information > Baseband version.Affected if The baseband version cannot be verified as patched by Samsung, or if the firmware version predates vendor security updates for this CVE.
-
Determine if cellular baseband is activeVerify that the device has cellular connectivity capabilities and the baseband processor is actively handling calls or data. Check if airplane mode is off and the device has cellular service active.Affected if Cellular baseband functionality is enabled and the device uses an affected Exynos chipset.
-
Review device vendor security advisoriesCheck the device manufacturer's security update page or release notes for information on CVE-2024-39890 patches. Identify if the device has received firmware updates that address this baseband vulnerability.Affected if The device manufacturer has not released or applied a patch for CVE-2024-39890 to the baseband firmware.
A user is affected if their device contains any of the listed Exynos chipsets (Modem 5123, Modem 5300, 9820, 9825, 980, 990, 850, or 1080) and the baseband firmware has not been updated to address the improper Call Control length field validation vulnerability.
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 updates from Samsung for affected processors and modems. Monitor for patches from device manufacturers using these chipsets.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39890 — 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-39890 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