dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20741

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to after 7.6.7.2 or later.
See remediation →
69/100
Remediation priority · Elevated
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 incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: WCNCR00434422; Issue ID: MSV-3958.

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 confidence

A WLAN AP driver contains an out-of-bounds write vulnerability caused by an incorrect bounds check. An attacker who already possesses System-level privileges can exploit this to write beyond allocated memory boundaries, achieving local privilege escalation. No user interaction is required for exploitation.

MitigationApply vendor patch WCNCR00434422 to the affected WLAN AP driver. Until the patch is available, restrict System-level access and monitor for unusual driver behavior.

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

CVSS:3.1/AV:L/AC:L/PR:H/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 operating environment
    Determine if the system runs Mediatek Software Development Kit or Openwrt by checking /etc/os-release or similar system identification files
    Affected if The system is identified as Mediatek SDK or Openwrt 19.07.0 or 21.02.0
  2. Check Mediatek SDK version
    Inspect the SDK version file typically located in /etc/version, /etc/rc.conf, or via 'cat /proc/version' if running Mediatek-based firmware
    Affected if The reported version is 7.6.7.2 or lower
  3. Verify Openwrt version
    Run 'cat /etc/openwrt_version' or 'cat /etc/os-release' to obtain the exact Openwrt release version
    Affected if The version is exactly 19.07.0 or 21.02.0
  4. Confirm WLAN AP driver presence
    Check for loaded wireless driver modules via 'lsmod | grep -i wlan' or inspect kernel module directory /lib/modules for mediatek wlan driver files
    Affected if A Mediatek WLAN AP driver module is loaded or present in the system
  5. Verify WLAN AP interface status
    Run 'iwconfig' or 'ip link show' to list wireless interfaces and check if an AP mode interface exists
    Affected if A wireless interface configured in AP (access point) mode is active
  6. Assess System-level access controls
    Review user accounts and group memberships via 'cat /etc/passwd' and check for unauthorized privileged accounts
    Affected if Multiple accounts with System-level or root privileges exist beyond known administrators

The system is affected if it runs Mediatek SDK version 7.6.7.2 or lower, or Openwrt version 19.07.0 or 21.02.0, and has the Mediatek WLAN AP driver enabled with a System-level attacker present.

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.2
Interim mitigation

Apply vendor patch WCNCR00434422 to the affected WLAN AP driver. Until the patch is available, restrict System-level access and monitor for unusual driver behavior.

Recommended fix Moderate confidence

Contact MediaTek for the fixed SDK version (versions > 7.6.7.2 may contain the fix)

  1. 1. Identify the MediaTek WLAN driver version currently in use by checking the SDK or OpenWrt package management system
  2. 2. Contact MediaTek directly to obtain the patch WCNCR00434422 or the fixed SDK release
  3. 3. For OpenWrt 19.07.0 and 21.02.0, check if vendor-supplied updates are available for the mediatek-firmware or mt76 driver packages
  4. 4. Apply the vendor patch or upgrade to the fixed release once identified
  5. 5. Verify the fix resolves the heap-based buffer overflow by testing WLAN AP functionality

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

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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