CVE-2025-61617
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 · uneditedIn nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional execution privileges needed
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 remote denial of service vulnerability exists in 5G NR (New Radio) modem components due to improper input validation. An attacker can send specially crafted inputs to the modem that trigger a system crash, causing the device to become unresponsive without requiring any elevated privileges.
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 data= 13.0= 14.0= 15.0= 16.0CVSS 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 Android versionCheck the device Settings > About Phone > Android version to confirm the exact installed versionAffected if The installed version matches 13.0, 14.0, 15.0, or 16.0 exactly
-
Determine if the device has 5G NR modem capabilityCheck the device specifications or modem firmware details to verify if the hardware includes 5G NR (New Radio) modem supportAffected if The device contains a 5G NR modem component
-
Verify if 5G connectivity is enabledInspect the device network settings under Settings > Network & Internet > Mobile Network to see if 5G or 5G NR is turned onAffected if 5G NR is enabled and active on the device
-
Confirm modem accessibilityCheck whether the modem component can receive external inputs, typically through mobile network interfaces or diagnostic portsAffected if The modem can accept network inputs from cellular connections
A device is affected if it runs Android 13.0, 14.0, 15.0, or 16.0 and contains an active 5G NR modem component that can receive external inputs.
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.
dbcve · scopedImplement proper input validation on all data paths entering the modem component, including boundary checks, type validation, and length verification. Apply vendor-supplied firmware/security updates for the affected modem when available.
- Contact Unisoc (www.unisoc.com) to obtain the modem firmware patch for the nr modem improper input validation vulnerability
- Apply the Unisoc modem firmware patch to the affected device through the OEM's standard update mechanism
- Device OEMs must integrate the Unisoc modem patch into their Android system updates for versions 13.0, 14.0, 15.0, and 16.0
- Users should apply the resulting OEM/Carrier Android security update that includes the Unisoc modem fix
- Verify the patch has been applied by checking the baseband/modem firmware version with the OEM or through device settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61617 — 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-61617 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