CVE-2025-20664
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 wlan AP driver, there is a possible information disclosure due to an uncaught exception. This could lead to remote (proximal/adjacent) information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00406217; Issue ID: MSV-2773.
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 confidenceIn the WLAN AP driver, an uncaught exception can lead to information disclosure. This driver-level flaw allows remote adjacent attackers within wireless range to potentially access sensitive data from memory without requiring any privileges or user interaction. The vulnerability stems from missing exception handling in the driver's code path.
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<= 7.4.0.1<= 7.6.7.2<= 8.2.1.4all 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Mediatek chipset modelCheck the device hardware specifications, boot logs, or network interface details to determine if the WLAN hardware uses an affected Mediatek chipset (Mt7915, Mt7916, Mt7981, Mt7986, Mt7990, or Mt7992)Affected if The device contains any of the affected chipset models listed in the CVE
-
Check the WLAN firmware or driver versionRetrieve the installed WLAN AP driver or firmware version from the device's system information, typically via CLI commands like 'iw list', 'wlan-cli', or through the device's web interface under wireless or firmware sectionsAffected if The version falls within the affected ranges: SDK <= 7.4.0.1, SDK <= 7.6.7.2, SDK <= 8.2.1.4, or for chipsets Mt7915/Mt7916/Mt7981/Mt7986/Mt7990/Mt7992 all versions are affected
-
Verify WLAN AP mode is enabledCheck the device configuration to confirm that the wireless access point functionality is actively running, typically via 'iwconfig', 'hostapd' status, or the device's wireless settings interfaceAffected if WLAN AP mode is enabled and the device is acting as a wireless access point
-
Review wireless interface logs for exceptionsExamine system or kernel logs (dmesg, /var/log/messages, or vendor-specific logs) for uncaught exceptions or error messages related to the WLAN driver that may indicate the vulnerability is being triggeredAffected if Uncaught exceptions or memory-related errors appear in the WLAN driver logs
A defender is affected if their device uses any of the listed Mediatek chipsets or SDK versions with WLAN AP mode enabled and the installed version falls within the affected ranges.
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 (WCNCR00406217) to affected WLAN AP devices. If patches are unavailable, consider network segmentation to limit exposure and monitor for anomalous wireless activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20664 — 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-20664 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