dbcve.org
Mt7603 FirmwareOperating system · Mediatek

CVE-2022-26442

MEDIUM · 6.7 CVSS v3.1 Published 2022-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220420051; Issue ID: GN20220420051.

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

A missing bounds check in a wifi driver allows an out of bounds write, enabling local privilege escalation to System level without user interaction. This is a memory corruption vulnerability in driver code.

MitigationApply the vendor patch (GN20220420051) to the affected wifi driver. Since this is a driver-level vulnerability, ensure the patch is tested for compatibility with the wireless stack before production deployment.

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
Mt7603 FirmwareOperating system
Affected:= 7.6.2.3
Mt7610 FirmwareOperating system
Affected:= 7.6.2.3
Mt7612 FirmwareOperating system
Affected:= 7.6.2.3
Mt7613 FirmwareOperating system
Affected:= 7.6.2.3
Mt7615 FirmwareOperating system
Affected:= 7.6.2.3
Mt7620 FirmwareOperating system
Affected:= 7.6.2.3
Mt7622 FirmwareOperating system
Affected:= 7.6.2.3
Mt7628 FirmwareOperating system
Affected:= 7.6.2.3

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

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

  1. Identify Mediatek wifi hardware in the system
    Examine system hardware information or network interface details to determine if a Mediatek wireless adapter is present. Look for device identifiers or chipset information matching Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628.
    Affected if The system does not contain any of the listed Mediatek chip models (no hardware match)
  2. Confirm the specific Mediatek chip model
    Retrieve detailed hardware or wireless adapter specification data to identify the exact chipset version. Cross-reference against the eight affected models listed.
    Affected if The identified Mediatek chip is not one of: Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628
  3. Check the installed wifi firmware version
    Query the wireless firmware or driver version information through system utilities, device management interfaces, or firmware retrieval methods specific to the Mediatek hardware. Compare the version string to 7.6.2.3.
    Affected if The firmware version is not exactly 7.6.2.3 (version mismatch)
  4. Verify the wifi driver is loaded and active
    Check if the wireless interface is enumerated, the driver module is loaded, or the wifi functionality is enabled on the system. This vulnerability requires the driver code to be executing.
    Affected if The wifi driver is not loaded or the wireless interface is not active

A system is affected only if it contains one of the eight listed Mediatek chips with firmware version exactly 7.6.2.3 and has the vulnerable wifi driver loaded and active.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (GN20220420051) to the affected wifi driver. Since this is a driver-level vulnerability, ensure the patch is tested for compatibility with the wireless stack before production deployment.

Recommended fix Moderate confidence

Firmware version containing MediaTek patch GN20220420051 (obtain specific version from device OEM)

  1. Contact the device manufacturer (OEM/ODM) that uses the affected MediaTek WiFi chip (Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628)
  2. Request firmware update incorporating MediaTek patch ID GN20220420051
  3. Apply the manufacturer-provided patched firmware to the device
  4. Verify the firmware version post-update matches the patched release
Caveat Firmware updates may require device downtime and should be tested in a staging environment before production deployment

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

Fix this in Mt7603 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26442 — 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-2022-26442 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