dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20654

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-07
Fix available
A fix is available. Upgrade to after 7.6.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In wlan service, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00406897; Issue ID: MSV-2875.

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 confidence

An out-of-bounds write vulnerability in the WLAN service stems from an incorrect bounds check, enabling remote code execution without requiring any privileges or user interaction. This critical flaw affects the wireless connectivity subsystem, likely at the firmware or driver level.

MitigationApply the vendor-supplied firmware patch (WCNCR00406897) to all affected devices through the standard firmware update mechanism.

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
Software Development KitApplication
Affected:<= 7.4.0.1<= 7.6.7.0
Mt7622Hardware / appliance
Affected:all versions
Mt7915Hardware / appliance
Affected:all versions
Mt7916Hardware / appliance
Affected:all versions
Mt7981Hardware / appliance
Affected:all versions
Mt7986Hardware / appliance
Affected:all versions
OpenwrtOperating system
Affected:= 19.07.0= 21.02.0
Mt6890Hardware / appliance
Affected:all versions

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model and chipset
    Run `cat /proc/cpuinfo` or check the device's physical label to determine the model. For Mediatek chipsets, check `/sys/class/ieee80211/` or use `iw list` to see the wireless driver info.
    Affected if The device uses a Mediatek Mt7622, Mt7915, Mt7916, Mt7981, Mt7986, or Mt6890 chipset, or runs OpenWrt 19.07.0 or 21.02.0, or uses Mediatek SDK versions 7.4.0.1 or earlier, or 7.6.7.0 or earlier.
  2. Check the WLAN firmware version
    For Mediatek devices, run `wlanconfig` or check `/etc/wireless/` directory contents. On OpenWrt, run `cat /etc/os-release` to confirm the exact version. Use `mt76-utility` or vendor-specific tools if available to query the WLAN firmware version.
    Affected if The firmware version is unpatched (the vendor patch WCNCR00406897 has not been applied). For SDK users, version is <= 7.4.0.1 or <= 7.6.7.0.
  3. Verify the WLAN service is enabled
    Run `ifconfig` or `ip link show` to list network interfaces. Check if a wireless interface (typically wlan0, ra0, or similar) exists and is up. On OpenWrt, run `wifi status` to confirm wireless is active.
    Affected if The WLAN service is running and a wireless interface is active. The vulnerability is in the WLAN service component, so the device is only affected when wireless is enabled.
  4. Check the driver version if accessible
    Run `modinfo mt76` or `lsmod | grep mt` to see loaded Mediatek wireless driver modules. On some devices, `cat /proc/net/mt76/*` may show driver and firmware info.
    Affected if The driver/firmware combination is from an unpatched Mediatek SDK or the device has not received the vendor firmware update.

You are affected if your device uses any of the listed Mediatek chipsets or OpenWrt versions AND the WLAN service is enabled AND the firmware/driver has not been patched with the vendor-supplied update (WCNCR00406897).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 7.6.7.0
Interim mitigation

Apply the vendor-supplied firmware patch (WCNCR00406897) to all affected devices through the standard firmware update mechanism.

Recommended fix Moderate confidence

Contact MediaTek for the fixed SDK version (beyond 7.4.0.1 and 7.6.7.0) containing patch WCNCR00406897

  1. Contact MediaTek technical support to obtain the specific firmware/hotfix that includes patch ID WCNCR00406897 for your affected chip platform (Mt7622, Mt7915, Mt7916, Mt7981, Mt7986, or Mt6890)
  2. If using OpenWRT 19.07.0 or 21.02.0, check for MediaTek-driven kernel/firmware updates that address MSV-2875
  3. After applying the update, verify the WLAN service is functioning correctly and no new vulnerabilities are introduced
  4. Monitor corp.mediatek.com for any official security advisory release regarding CVE-2025-20654

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20654 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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