CVE-2025-20644
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, there is a possible memory corruption due to incorrect error handling. This could lead to remote denial of service, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01525673; Issue ID: MSV-2747.
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 exists in the modem firmware of mobile devices. Incorrect error handling during certain base station communications leads to memory corruption, which can be exploited by a rogue base station to cause remote denial of service. The attack requires no user interaction or elevated privileges, only that a User Equipment (UE) connects to an attacker-controlled base station.
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 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 modem chipset in your deviceCheck device specifications, settings (About Phone > Baseband or Modem), or use AT command 'ATI' via a terminal app or serial connection to query the modem for its model informationAffected if The modem chipset is identified as a Mediatek Nr15 or Mediatek Nr16 model
-
Retrieve the current modem firmware versionUse AT command 'AT+CGMR' or check the device's baseband/modem information in system settings to obtain the installed firmware versionAffected if The firmware version is present and can be compared against the patched version
-
Verify the patch MOLY01525673 has been appliedCross-reference your extracted firmware version with Mediatek's patch release notes or contact the device OEM to confirm whether the MOLY01525673 patch is included in your current modem firmwareAffected if The patch is not confirmed as applied, or the device OEM has not released an update containing this patch
You are affected if your device contains a Mediatek Nr15 or Nr16 modem and the vendor-supplied patch MOLY01525673 has not been applied to the modem firmware.
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 the vendor-supplied modem firmware patch (MOLY01525673) to affected devices. Until patched, users should avoid connecting to untrusted or unknown base stations, though this is difficult to control at the user level.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20644 — 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-20644 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