CVE-2025-20675
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 system crash due to an uncaught exception. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00413201; Issue ID: MSV-3302.
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 confidenceThe wlan STA (Wireless LAN Station) driver contains an uncaught exception that causes a system crash, leading to local denial of service. Exploitation requires User execution privileges but no user interaction. The vulnerability exists in the driver's exception handling path.
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<= 3.6<= 3.6<= 3.6<= 3.6<= 3.6CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Mediatek wireless hardware presentRun 'lspci -v | grep -i mediatek' or 'lsusb' to list wireless adapters. Look for devices with chip IDs Mt7902, Mt7921, Mt7922, Mt7925, or Mt7927.Affected if A Mediatek wireless adapter matching one of these model numbers is installed.
-
Retrieve wireless firmware versionCheck the firmware version loaded for the Mediatek adapter. Use 'iw dev' or check /lib/firmware/mediatek/ for loaded firmware files. Alternatively, examine dmesg output for firmware version strings at boot.Affected if The firmware version displayed is 3.6 or lower, or the version string cannot be determined (indicating it may be an unpatched older release).
-
Verify wlan STA driver is activeRun 'lsmod | grep -i mt7' or check 'iw list' to confirm the Mediatek STA (Station) driver module is loaded and the wireless interface is active (up state).Affected if The wlan STA driver module for Mediatek is loaded and a wireless interface exists.
-
Check for driver crash logsReview system logs (journalctl -b, dmesg, or /var/log/syslog) for entries mentioning 'wlan STA', 'WiFi', or 'mediatek' related crashes, exceptions, or kernel panics. Also check for crash dump files in /var/crash/ if present.Affected if Recent crash logs or dump files reference the Mediatek wlan STA driver exception handling path.
The system is affected if it contains a Mediatek Mt7902, Mt7921, Mt7922, Mt7925, or Mt7927 wireless adapter running firmware version 3.6 or lower with the wlan STA driver active.
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 WCNCR00413201 to update the wlan STA driver. If patch unavailable, consider network isolation or disabling WiFi as temporary mitigation until update is possible.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20675 — 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-20675 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