CVE-2025-20683
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 with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00416938; Issue ID: MSV-3444.
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 causes an out-of-bounds write vulnerability, enabling local privilege escalation without user interaction. This is a memory corruption flaw in the wireless driver that can be exploited to gain elevated privileges on the affected system.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the platform running the wireless APCheck system information to determine if the device runs Mediatek Software Development Kit or Openwrt. Look for manufacturer details, firmware identifiers, or OS package listings.Affected if The platform is Mediatek SDK or Openwrt versions 19.07.0 or 21.02.0
-
Check the Mediatek SDK versionIf running Mediatek-based firmware, retrieve the SDK version through firmware metadata, system build information, or driver package version listings. Common locations include /etc/version, /proc/version, or vendor-specific diagnostic interfaces.Affected if The SDK version is 7.6.7.2 or earlier
-
Check the Openwrt versionIf running Openwrt, run 'cat /etc/openwrt_version' or 'cat /etc/os-release' to retrieve the installed Openwrt version.Affected if The installed version is exactly 19.07.0 or exactly 21.02.0
-
Verify the wlan AP driver is loadedCheck if the wireless access point driver module is currently loaded or active on the system. Use commands like 'lsmod', 'iwconfig', or 'ip link show' to enumerate wireless interfaces operating in AP mode.Affected if A wireless interface is configured in AP (access point) mode and the driver is active
A system is affected if it runs Mediatek SDK version 7.6.7.2 or earlier, or Openwrt version 19.07.0 or 21.02.0, AND has the wlan AP driver loaded with an active access point interface.
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 (WCNCR00416938) to the WLAN AP driver to correct the bounds checking logic. Given the critical severity (9.8) and privilege escalation impact, prioritize patching across affected deployments.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20683 — 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-20683 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