dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20710

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to after 7.6.7.2 or later.
See remediation →
93/100
Remediation priority · Urgent
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 AP driver, there is a possible out of bounds write due to an integer overflow. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00418785; Issue ID: MSV-3515.

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

In a WLAN AP driver, an integer overflow vulnerability allows an attacker within wireless range (proximal/adjacent) to trigger an out-of-bounds write beyond allocated buffer boundaries, potentially achieving privilege escalation. The vulnerability requires no user interaction and no additional execution privileges, making it a high-severity local network threat.

MitigationApply the vendor patch (WCNCR00418785) by updating the WLAN driver firmware or software to the patched version. Prioritize devices with direct AP functionality in high-density wireless environments.

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.6.7.2
OpenwrtOperating system
Affected:= 19.07.0= 21.02.0

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 Mediatek SDK WLAN driver version
    Check the WLAN driver firmware or software version on the device. On Mediatek-based APs, this is typically found via 'wlanconfig' command, 'iw list', or checking /proc/mt_wifi version files. Run: 'cat /proc/mt_wifi/version' or 'wlanconfig ath0 version' if available.
    Affected if The driver version is 7.6.7.2 or earlier (any version <= 7.6.7.2)
  2. Identify Openwrt WLAN AP version
    Check the Openwrt version installed on the device. Run: 'cat /etc/openwrt_release' or 'cat /etc/os-release' to display the installed version string.
    Affected if The installed version is exactly 19.07.0 or exactly 21.02.0
  3. Confirm WLAN AP mode is enabled
    Verify that the device has an Access Point (AP) or Master mode interface active. Run: 'iwconfig' or 'ip link show' to list wireless interfaces, then 'iwconfig <interface>' to check if mode=Master or AP is configured.
    Affected if At least one wireless interface is configured in AP/Master mode on a Mediatek SDK <= 7.6.7.2 or Openwrt 19.07.0/21.02.0 system
  4. Check for Mediatek Wi-Fi driver modules
    On Linux-based systems with Mediatek chipsets, verify the mt76 driver or mt_wifi module is loaded. Run: 'lsmod | grep -E "mt76|mt_wifi"' or check kernel module directory: 'ls /lib/modules/$(uname -r)/kernel/drivers/net/wireless/mediatek/'
    Affected if Mediatek wireless drivers (mt76/mt_wifi) are present and the SDK version is <= 7.6.7.2
  5. Verify WLAN AP functionality is in use
    Confirm the device is acting as an AP by checking hostapd configuration or wireless settings. Run: 'ps | grep hostapd' or examine /etc/config/wireless in Openwrt to list configured APs.
    Affected if The device is configured to run as a WLAN Access Point using the vulnerable Mediatek driver or Openwrt version

You are affected if your device runs Mediatek SDK <= 7.6.7.2 OR Openwrt 19.07.0/21.02.0 with an active WLAN AP interface using Mediatek wireless drivers.

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.

From vendor data
Upgrade available Upgrade to a release after 7.6.7.2
Interim mitigation

Apply the vendor patch (WCNCR00418785) by updating the WLAN driver firmware or software to the patched version. Prioritize devices with direct AP functionality in high-density wireless environments.

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20710 — 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-20710 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