dbcve.org
Mt7902 FirmwareOperating system · Mediatek

CVE-2025-20673

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-02
Fix available
A fix is available. Upgrade to after 3.6 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
In 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: WCNCR00413200; Issue ID: MSV-3304.

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 confidence

In the wlan STA (Wireless LAN Station) driver, an uncaught exception can trigger a system crash, resulting in local denial of service. The vulnerability is exploitable locally with User execution privileges and requires no user interaction.

MitigationApply the vendor patch (WCNCR00413200) to implement proper exception handling in the WLAN STA driver, preventing uncaught exceptions from causing system crashes.

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
Mt7902 FirmwareOperating system
Affected:<= 3.6
Mt7921 FirmwareOperating system
Affected:<= 3.6
Mt7922 FirmwareOperating system
Affected:<= 3.6
Mt7925 FirmwareOperating system
Affected:<= 3.6
Mt7927 FirmwareOperating system
Affected:<= 3.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the wireless chipset
    Run 'lspci | grep -i network' or 'iw dev' to list wireless adapters. For USB adapters, use 'lsusb'.
    Affected if The adapter uses a Mediatek Mt7902, Mt7921, Mt7922, Mt7925, or Mt7925 chipset.
  2. Check the driver in use
    Run 'iw dev <interface> info' or check '/sys/class/net/<interface>/device/driver' to identify the driver bound to the wireless interface.
    Affected if The driver is a Mediatek WLAN STA driver (such as mt7921e, mt7922e, mt7925e, etc.).
  3. Verify STA mode is active
    Run 'iw dev <interface> link' or 'iwconfig <interface>' to confirm the interface is in Station (managed) mode and associated to an AP.
    Affected if The interface is operating in Station mode (managed mode) as the vulnerable code path is in the STA driver.
  4. Check firmware version
    For Mediatek adapters, check the firmware version via 'cat /sys/class/net/<interface>/device/firmware_version' or inspect the firmware file loaded (typically in /lib/firmware/mediatek/). Compare the version number to the affected range.
    Affected if The firmware version is 3.6 or lower, or if the version cannot be determined but the chipset and driver match the affected products.

A system is affected if it uses any of the listed Mediatek chipsets (Mt7902, Mt7921, Mt7922, Mt7925, Mt7927) with firmware version 3.6 or lower and operates in Station (client) mode.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.6
Interim mitigation

Apply the vendor patch (WCNCR00413200) to implement proper exception handling in the WLAN STA driver, preventing uncaught exceptions from causing system crashes.

Recommended fix Moderate confidence

Firmware version > 3.6 with patch WCNCR00413200 applied (contact MediaTek or device vendor for exact version)

  1. Contact the device manufacturer to obtain firmware updates incorporating MediaTek patch WCNCR00413200 for the affected WiFi chip (Mt7902, Mt7921, Mt7922, Mt7925, or Mt7927)
  2. If you are an OEM/ODM integrating MediaTek chips, request the patched firmware from MediaTek directly referencing patch ID WCNCR00413200 / issue ID MSV-3304
  3. Apply the updated firmware to devices following the manufacturer's standard firmware update procedure
  4. Verify the system no longer exhibits crashes in the WLAN STA driver after the update
Caveat Firmware updates may require device reboot; ensure compatibility with the specific device model before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mt7902 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20673 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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