CVE-2025-26784
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 NAS in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, W920, W930, W1000, Modem 5123, Modem 5300, Modem 5400. The lack of a length check leads to out-of-bounds writes.
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 confidenceA missing length check in the NAS (Non-Access Stratum) layer of Samsung's baseband processor firmware allows out-of-bounds memory writes. This vulnerability affects multiple Exynos mobile, wearable, and modem chipsets, and could be exploited via malformed NAS messages from a malicious cell tower to corrupt memory in the baseband processor.
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 baseband chipset in your deviceCheck the device specifications or system information to determine the Exynos processor model. On Android devices, this is typically found in Settings > About Phone > Chipset or through diagnostic apps like CPU-Z. On Samsung devices, check the model number and compare against the chipset list for your specific device variant.Affected if The device uses an Exynos 980, 990, 850, 1080, 2100, 1280, 2200, or 1330 chipset for cellular baseband processing
-
Confirm the device has cellular baseband firmwareVerify that the device includes a cellular modem. Check if the device has SIM card capability and shows cellular network information (carrier name, signal strength, mobile network type) in the status bar or Settings > Connections > Mobile Networks.Affected if The device contains an active cellular baseband processor with firmware (this excludes Wi-Fi-only devices)
-
Check if cellular radio is enabledInspect whether the device's cellular radio is turned on. On Android, go to Settings > Connections > Mobile Networks and verify the Mobile Data toggle or Airplane Mode status. A disabled cellular radio reduces exposure.Affected if Cellular service is enabled and the device can connect to cell towers, making it potentially reachable by malicious base stations
-
Assess physical exposure to cellular networksEvaluate the device usage context: is it a mobile phone used in public areas, a wearable carried during travel, or a stationary device? Devices that operate in areas with untrusted or unmonitored cell tower coverage have higher exposure to rogue base station attacks.Affected if The device operates in environments where it may connect to untrusted or malicious cell towers (e.g., public mobile use, travel to unfamiliar areas)
You are affected if your device contains one of the listed Exynos chipsets (980, 990, 850, 1080, 2100, 1280, 2200, 1330) and has cellular connectivity enabled, as the missing NAS length check vulnerability exists in all firmware versions of these chipsets and can be exploited via malformed messages from a rogue cell tower.
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 chipsets. Until patches are available, consider using alternative cellular hardware or network segmentation to reduce exposure to rogue cell towers.
- Consultation4.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,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26784 — 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-26784 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