CVE-2025-20732
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 (when OceReducedNeighborReport is disabled). User interaction is not needed for exploitation. Patch ID: WCNCR00441510; Issue ID: MSV-4139.
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 confidenceOut-of-bounds write vulnerability in the WLAN AP driver due to incorrect bounds checking in neighbor report handling. When OceReducedNeighborReport is disabled, a local attacker with existing System-level privileges can trigger the vulnerability to achieve privilege escalation without user interaction.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 system product and WLAN driverRun 'uname -a' or check '/etc/os-release' to determine if the system is running Mediatek SDK or OpenWrt. For Mediatek, check the WLAN driver module via 'lsmod | grep -i wlan' or 'modinfo mt76'Affected if The system is not running Mediatek SDK or OpenWrt - the detection does not apply
-
Check the installed version against affected rangesFor Mediatek SDK, check the SDK version via 'cat /etc/version' or check the firmware version. For OpenWrt, run 'cat /etc/openwrt_version' or 'cat /etc/os-release' to get the exact version numberAffected if Mediatek SDK version is greater than 7.6.7.2, or OpenWrt version is neither 19.07.0 nor 21.02.0 - likely not affected
-
Verify if OceReducedNeighborReport is disabledCheck the WLAN AP driver configuration for the OceReducedNeighborReport setting. This may be found in the driver config file, via 'iwpriv' or 'iw' commands such as 'iwpriv [interface] get_para' or by examining the driver module parameters with 'modinfo mt76' and looking for related parameters. If available, check if it is explicitly set to disabled or 0Affected if OceReducedNeighborReport is explicitly disabled, the system is vulnerable when combined with the affected versions
-
Confirm the WLAN AP driver is loadedCheck that the WLAN AP driver is active by running 'iwconfig' or 'ip link show' to list wireless interfaces, or 'lsmod | grep mt' for Mediatek driversAffected if No WLAN AP driver is loaded or active - the vulnerability cannot be triggered
The system is affected if it runs Mediatek SDK <= 7.6.7.2 or OpenWrt 19.07.0/21.02.0, uses the affected WLAN AP driver, and has OceReducedNeighborReport disabled.
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 vendor patch WCNCR00441510 to address the bounds check error. Additionally, enable the OceReducedNeighborReport feature as a defense-in-depth measure if supported, and strictly limit System-level access to trusted local users.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20732 — 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-20732 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