CVE-2025-36912
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 cellular modem, there is a possible denial of service due to a logic error in the code. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.
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 logic error in cellular modem firmware allows remote attackers to cause denial of service without authentication or user interaction. The vulnerability stems from improper state handling or conditional logic in the modem's code path, leading to a condition where the modem becomes unresponsive or crashes.
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 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm device has cellular modem capabilityVerify the Android device has cellular/phone functionality (not Wi-Fi only). Check if the device can make cellular calls or shows a SIM card status in Settings > About Phone > SIM Status.Affected if Device has cellular capability (most Android phones/tablets do)
-
Identify cellular modem firmware versionAccess the modem firmware version via AT command interface. Using a terminal app or ADB shell, attempt to run: AT+CGMR or check /proc/at_utils/modem_version, or look under Settings > About Phone > SIM Status for Baseband or Modem version information.Affected if Unable to determine modem firmware version, or version is unpatched (no fixed version range provided in CVE)
-
Verify modem is network-accessibleConfirm the cellular modem is actively registered on a mobile network. Check for signal bars and network type (4G/5G) in the status bar. The vulnerability allows remote DoS, so the modem must be connected to a carrier network.Affected if Modem shows no cellular connection or signal
-
Check for modem responsivenessTest if the cellular modem responds to AT commands. Use a terminal or ADB to send: AT to the modem. A responsive modem returns OK. An unresponsive modem indicates the DoS condition.Affected if Modem does not respond to AT commands or shows repeated failures
User is affected if the Android device has an active cellular modem with firmware containing the logic error causing unresponsiveness, as no specific fixed version ranges are provided for this CVE.
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 patches for the cellular modem. If no patch is available, consider network segmentation or alternative modem hardware until an update is provided.
- Consultation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36912 — 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-36912 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