CVE-2025-71255
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 Modem IMS, there is a possible 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 confidenceThis vulnerability in Modem IMS (IP Multimedia Subsystem) involves improper input validation that can be exploited remotely to cause denial of service without requiring any elevated privileges. The issue allows attackers to send specially crafted inputs that crash or render the IMS service unavailable.
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 installed Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Android version is 13.0, 14.0, 15.0, or 16.0
-
Determine if device has cellular modem with IMSCheck if device has cellular/SIM capability - look for SIM card slot, or run 'getprop ro.telephony.default_network' via ADB to confirm cellular presenceAffected if Device is a cellular-capable Android phone (non-WiFi-only)
-
Check if IMS is enabled on the deviceGo to Settings > Network & Internet > SIMs > [SIM name] > Advanced > IMS, or check Settings > Connections > Mobile Networks for VoLTE/5G options that indicate IMS is activeAffected if IMS or VoLTE/5G is turned on in phone settings (this enables the vulnerable component)
-
Verify modem/baseband firmware version if accessibleGo to Settings > About Phone > SIM Status > Carrier or run 'getprop gsm.version.baseband' via ADB shell - note that vendor-specific patch levels may be reflected hereAffected if Modem firmware is at a version predating the vendor patch for this CVE (patch date unknown - compare against future vendor releases)
You are affected if you run Android 13.0, 14.0, 15.0, or 16.0 on a cellular-capable device with IMS enabled, and your device has not yet received a vendor-specific modem IMS patch.
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 · scopedApply vendor patches for Modem IMS that address input validation logic, and implement network-level filtering to reject malformed IMS messages at the perimeter until the patch can be deployed.
- Contact your device manufacturer or mobile carrier to request a modem/baseband firmware update that addresses CVE-2025-71255
- Verify with the vendor that the update includes the Unisoc modem IMS fix for improper input validation
- After applying the firmware update, confirm the vulnerability is resolved through security testing or vendor confirmation
- Monitor your device manufacturer's security bulletins for future modem-related patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-71255 — 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-71255 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