CVE-2025-20693
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 STA driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote (proximal/adjacent) information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09812521; Issue ID: MSV-3421.
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 confidenceA bounds check error in the WLAN station driver causes an out-of-bounds memory read, allowing adjacent attackers to potentially obtain sensitive information from device memory without authentication or 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= 4.0<= 3.7= 13.0= 14.0= 15.0= 21.02.0= 23.05CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Mediatek WLAN hardware in useCheck system hardware info or network interfaces for Mediatek wireless chipsets (e.g., via lspci, lsusb, or /proc/bus/pci/devices)Affected if Mediatek WLAN hardware is present and the driver is the Mediatek station driver
-
Check Mediatek SDK versionLocate the Mediatek Software Development Kit installation and query its version (typically found in SDK documentation, build files, or firmware metadata)Affected if SDK version is <= 3.7 and uses the affected WLAN STA driver
-
Verify Android versionCheck the device Android version in Settings > About Phone or via 'getprop ro.build.version.release'Affected if Android version is 13.0, 14.0, or 15.0 with Mediatek WLAN driver
-
Check Linuxfoundation Yocto versionQuery the Yocto build version from /etc/lsb-release, build metadata, or image version fileAffected if Yocto version is exactly 4.0 with the vulnerable WLAN driver included
-
Verify OpenWRT versionCheck OpenWRT version via 'cat /etc/openwrt_release' or 'opkg list-installed'Affected if OpenWRT version is 21.02.0 or 23.05 with Mediatek WLAN support
-
Confirm WLAN station mode is activeCheck if wireless interface is configured in station (STA) mode via iwconfig, iw, or network configuration filesAffected if WLAN station mode is enabled on a Mediatek wireless interface
The environment is affected if it runs any of the listed versions (Yocto 4.0, Mediatek SDK <=3.7, Android 13/14/15, OpenWRT 21.02.0/23.05) with Mediatek WLAN station driver and has WLAN station mode enabled.
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 (ALPS09812521) to update the WLAN STA driver firmware, ensuring proper bounds validation is implemented.
- Consultation3.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,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20693 — 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-20693 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