CVE-2025-57835
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 RRC in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. Improper memory initialization results in an illegal memory access, causing a system crash via a malformed RRCReconfiguration message.
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 confidenceImproper memory initialization in the RRC (Radio Resource Control) protocol implementation in Samsung Exynos baseband processors allows a remote attacker to cause a denial-of-service via a malformed RRCReconfiguration message. The improper initialization leads to illegal memory access, resulting in a system crash.
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 the device model and SoCCheck the device Settings > About Phone > Model number and Processor/SoC information to determine if the device uses a Samsung Exynos chipset. Common affected devices include Samsung Galaxy S20 series (Exynos 990), Galaxy A51/A71 (Exynos 980), various Galaxy A series phones (Exynos 850, 1080, 1280, etc.)Affected if The device is a Samsung phone or tablet using any of the following Exynos processors: 990, 980, 850, 1080, 1280, 1330, 1380, or 1480
-
Check the baseband firmware versionNavigate to Settings > About Phone > Software Information and locate the 'Baseband version' or 'Modem version' field. Record this version number for comparison.Affected if The baseband version corresponds to firmware for any of the affected Exynos processors listed in the CVE (all versions of Exynos 990, 980, 850, 1080, 1280, 1330, 1380, and 1480 firmware are affected)
-
Verify baseband vulnerability contextConfirm the device receives cellular service through the Exynos baseband modem. The vulnerability is triggered specifically by malformed RRCReconfiguration messages received over the cellular network.Affected if The device uses the Exynos baseband processor for cellular communication (2G/3G/4G/5G) and processes RRC protocol messages from the network
A user is affected if they own a Samsung device equipped with any of the listed Exynos baseband processors (990, 980, 850, 1080, 1280, 1330, 1380, 1480), as all firmware versions for these chipsets are vulnerable to improper memory initialization when processing RRCReconfiguration messages.
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 for affected Exynos processors and modems. No user-level workarounds exist as the vulnerability is triggered by receiving a maliciously crafted network message.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57835 — 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-2025-57835 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