CVE-2025-20659
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 system crash due to improper input validation. 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: MOLY01519028; Issue ID: MSV-2768.
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 confidenceThis is a modem vulnerability caused by improper input validation that can be exploited when a User Equipment (UE) connects to a rogue/malicious base station controlled by an attacker. The attacker can send specially crafted input via the base station that triggers a system crash in the modem, causing a denial of service condition. No user interaction or elevated privileges are required for exploitation.
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
- 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 modelCheck the device specifications or modem firmware information to determine if the chipset is one of the following: Mediatek Mt2735, Mt2737, Mt6739, Mt6761, Mt6762, Mt6762d, Mt6762m, or Mt6763Affected if The device uses any of these Mediatek chipset models
-
Check the modem firmware versionAccess the modem firmware settings or use AT commands (such as AT+CGMR or ATI) to query the installed firmware versionAffected if The firmware version cannot be verified or is unknown
-
Verify if vendor patch MOLY01519028 is appliedContact the device manufacturer or mobile network operator to confirm whether the patch MOLY01519028 has been applied to the modem firmwareAffected if The patch has not been applied or its status is unknown
-
Monitor for unexpected modem crashes or rebootsCheck system logs or modem diagnostic logs for unexplained crashes, hang-ups, or sudden reboots, particularly after connecting to new or unfamiliar base stationsAffected if The modem experiences unexplained crashes or denial of service conditions
A user is affected if their device contains a Mediatek Mt2735, Mt2737, Mt6739, Mt6761, Mt6762, Mt6762d, Mt6762m, or Mt6763 chipset and the vendor patch MOLY01519028 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 patch (MOLY01519028) to affected modem firmware. Users should avoid connecting to untrusted or unknown base stations, and network operators should monitor for rogue base station activity.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20659 — 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-20659 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