CVE-2025-53965
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 980, 990, 850, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. The function used to decode the SOR transparent container lacks bounds checking, which can cause a fatal error.
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 bounds checking vulnerability exists in the SOR transparent container decoding function across multiple Samsung Exynos processors and modems (980, 990, 850, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, W920, W930, W1000, Modem 5123, 5300, 5400). The missing bounds check can cause out-of-bounds memory access leading to a fatal error, potentially resulting in denial of service or arbitrary code execution.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 in your deviceCheck the processor/modem information on the device or in the system specifications. Common methods include: checking /proc/cpuinfo on Android devices, reviewing the device's technical specifications, or using a system info app.Affected if The device uses an Exynos 1280, 1330, 1380, 1480, 1580, 2100, 2200, or 2400 processor or modem chip.
-
Determine if SOR transparent container decoding is in useInspect the modem or baseband firmware configuration for any active SOR (Serial Optical Reception) transparent container decoding functionality. This typically requires access to modem debug logs, baseband analysis tools, or firmware configuration files.Affected if The SOR transparent container decoding feature or module is enabled and processing input data on the affected Exynos chipset.
-
Review modem/baseband firmware versionCheck the installed modem or baseband firmware version through the device's About Phone menu, engineering menus (*#*#4636#*#*), or via ADB commands like 'adb shell dumpsys iphonesubinfo' or manufacturer-specific diagnostic tools.Affected if The device runs any firmware version on an affected Exynos chipset, since all versions are vulnerable.
-
Check for unexpected modem or baseband crashesMonitor system logs (logcat, dmesg) or device crash reports for fatal errors, out-of-bounds memory access errors, or unexpected modem restarts that could indicate exploitation of this vulnerability.Affected if The device exhibits unexplained baseband crashes or fatal errors, particularly related to decoding operations.
A device is affected if it contains any of the listed Exynos processors (1280, 1330, 1380, 1480, 1580, 2100, 2200, 2400) and the SOR transparent container decoding feature is active, since all firmware versions of these chipsets are vulnerable.
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. Inventory all devices using these chipsets and prioritize patching for exposed/edge-facing systems.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53965 — 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-53965 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