CVE-2025-26783
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 2100, 1280, 2200, 1330, 1380, 1480, 2400, W1000, Modem 5300, and Modem 5400. Incorrect handling of undefined values leads to a Denial of Service.
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 confidenceDenial of Service vulnerability in the RRC (Radio Resource Control) protocol implementation of Samsung mobile processors (Exynos series) and modems. The issue involves incorrect handling of undefined values in the RRC layer, which can cause the modem to crash or become unresponsive, resulting in loss of cellular connectivity.
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 chipsetCheck the device settings or system information to determine if the processor is a Samsung Exynos chipset. On Android, go to Settings > About Phone > Processor or Chipset. Alternatively, check the device model number and search whether it uses an Exynos 2100, 1280, 2200, 1330, 1380, 1480, 2400, or W1000 processor.Affected if The device uses any of the listed Exynos chipsets (2100, 1280, 2200, 1330, 1380, 1480, 2400, or W1000)
-
Check the baseband/modem firmware versionOn Android, go to Settings > About Phone > Software Information and look for the Baseband version or Modem version. Alternatively, dial *#1234# or use a device info app to view modem firmware details.Affected if Any baseband firmware version is present on a device with the affected Exynos chipsets - all versions are vulnerable
-
Confirm cellular connectivity is enabledVerify that the device has cellular service active. Check that airplane mode is off and the device is connected to a mobile network. The RRC layer is only engaged when cellular radio is active.Affected if Cellular connectivity is enabled on a device with an affected Exynos chipset and modem firmware
A user is affected if their Samsung device uses any of the Exynos 2100, 1280, 2200, 1330, 1380, 1480, 2400, or W1000 chipsets and has cellular service enabled, as all firmware versions of these chipsets contain the RRC 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/security updates from Samsung for affected devices. Users should ensure automatic security updates are enabled and check for available updates from device manufacturers.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26783 — 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-26783 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