dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20748

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: WCNCR00432679; Issue ID: MSV-3950.

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

This is a local privilege escalation vulnerability in the WLAN AP driver. An incorrect bounds check leads to an out-of-bounds write condition, allowing an attacker who already has System-level privileges to escalate to higher privileges. No user interaction is required for exploitation.

MitigationApply the vendor patch (WCNCR00432679) to fix the bounds checking logic in the WLAN AP driver. Since the vulnerability requires System-level access, prioritize patching systems with elevated attack surfaces and restrict administrative access.

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 system product
    Determine if the target system is running Mediatek Software Development Kit or Openwrt. Check system documentation, firmware information, or run 'cat /etc/os-release' or 'uname -a' to identify the OS/product.
    Affected if The system is not Mediatek SDK or Openwrt - this CVE only applies to those specific products.
  2. Check Mediatek SDK version
    If Mediatek SDK is identified, run 'cat /etc/version' or check the SDK documentation to find the installed version number.
    Affected if Mediatek SDK version is 7.6.7.2 or lower.
  3. Check Openwrt version
    If Openwrt is identified, run 'cat /etc/openwrt_version' or 'cat /etc/os-release' to obtain the exact version.
    Affected if Openwrt version is exactly 19.07.0 or exactly 21.02.0.
  4. Verify WLAN AP driver is active
    Check if the WLAN AP driver is loaded or in use. Run 'lsmod' to list loaded kernel modules and look for wireless LAN driver modules, or check 'iwconfig' or 'ip link show' for wireless interfaces.
    Affected if The WLAN AP driver module is loaded and active on the system.

The system is affected only if it runs Mediatek SDK <= 7.6.7.2 OR Openwrt 19.07.0/21.02.0 AND has the WLAN AP driver enabled, allowing a locally authenticated attacker with System-level privileges to escalate privileges.

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 the vendor patch (WCNCR00432679) to fix the bounds checking logic in the WLAN AP driver. Since the vulnerability requires System-level access, prioritize patching systems with elevated attack surfaces and restrict administrative access.

Recommended fix Moderate confidence

MediaTek SDK > 7.6.7.2 (or OpenWrt version containing patched MediaTek WLAN driver with WCNCR00432679)

  1. 1. Identify the MediaTek Wi-Fi driver/SDK version currently in use
  2. 2. Obtain the latest MediaTek SDK or driver package from MediaTek's official channels or your device vendor
  3. 3. Upgrade the MediaTek SDK to a version newer than 7.6.7.2 which contains the security fix (Patch ID: WCNCR00432679)
  4. 4. For OpenWrt users: Upgrade to a newer OpenWrt release that includes the patched MediaTek driver
  5. 5. Reboot the device after applying the update
  6. 6. Verify the driver version matches the expected fixed release
Caveat Upgrade may require matching kernel/driver compatibility; ensure device vendor supports the target SDK version before upgrading

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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