CVE-2025-20715
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 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: WCNCR00421152; Issue ID: MSV-3731.
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 confidenceA bounds check error in the WLAN AP driver allows an out-of-bounds write, which can be leveraged for local privilege escalation from System privilege. The vulnerability resides in the driver's memory handling logic and requires no user interaction to exploit once the attacker has initial System-level 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<= 7.6.7.2= 19.07.0= 21.02.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SDK or firmware versionCheck the Mediatek SDK version by reviewing the system firmware/build documentation, version file, or running 'cat /etc/version' or 'uname -a' if accessible. For OpenWRT, run 'cat /etc/openwrt_version' or check the release file.Affected if The SDK version is 7.6.7.2 or lower, OR the OpenWRT version is exactly 19.07.0 or 21.02.0
-
Confirm Mediatek hardware is presentInspect the hardware specifications or boot logs for Mediatek chipset identifiers, or run 'lspci' or 'lsusb' to list hardware components and look for Mediatek wireless devices.Affected if The system contains Mediatek wireless hardware and the SDK version is at or below 7.6.7.2
-
Verify the WLAN AP driver is loadedCheck for loaded kernel modules related to wireless functionality using 'lsmod' or 'modprobe -l' and look for WLAN AP driver modules specific to Mediatek hardware.Affected if A Mediatek WLAN AP driver module is actively loaded in memory
-
Check for the vulnerable driver memory handlingReview driver logs or debug output for wireless subsystem messages, or inspect /proc/modules and /sys/module/ for the specific Mediatek wireless driver entry.Affected if The Mediatek WLAN AP driver version matches the affected SDK range and the driver is running
You are affected if the system runs Mediatek SDK version 7.6.7.2 or lower with an active WLAN AP driver, or runs OpenWRT 19.07.0 or 21.02.0 with Mediatek wireless hardware and the vulnerable driver loaded.
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 (WCNCR00421152) to update the WLAN AP driver firmware/software. Since this is a driver-level issue, the fix requires obtaining and deploying the patched driver from the vendor, not a configuration change.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20715 — 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-20715 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