dbcve.org
Mt7603 FirmwareOperating system · Mediatek

CVE-2022-26438

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: GN20220420013; Issue ID: GN20220420013.

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 the WiFi driver allows an out-of-bounds write vulnerability, enabling local privilege escalation from System execution level. The vulnerability requires no user interaction and can be exploited locally.

MitigationApply patch GN20220420013 to update the WiFi driver and remediate the missing bounds check. Verify all affected systems receive the driver update.

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 chipset in use
    Check system information, device specifications, or WiFi adapter details to determine if the system uses a Mediatek WiFi chip. Common methods: 'lspci' or 'lsusb' for adapter info, check /proc/bus/pci or /sys/class/net for network device details, or review device hardware documentation.
    Affected if The system does not use a Mediatek WiFi chipset from the Mt7xxx series (Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, Mt7628)
  2. Confirm specific chipset model
    Examine the WiFi adapter identifier to confirm the exact Mediatek model. Use commands like 'lspci -v', 'lsusb', 'iw list', or check network interface driver information via 'ethtool -i' or /proc/net/wireless.
    Affected if The chipset model is not one of: Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628
  3. Retrieve WiFi firmware version
    Query the installed WiFi driver or firmware version. This may be available via 'iw', 'wlanctl', vendor-specific tools, or by reading driver debug/info files in /sys or /proc. Check Mediatek driver module parameters or firmware file metadata if accessible.
    Affected if Unable to retrieve the WiFi firmware version from the driver
  4. Compare firmware version against affected release
    Compare the retrieved firmware version against the affected version 7.6.2.3. Ensure exact version match as specified in the affected products list.
    Affected if The installed WiFi firmware version is 7.6.2.3 on a listed Mediatek chipset
  5. Verify WiFi driver is loaded and active
    Confirm the WiFi interface is present and the Mediatek WiFi driver is loaded. Check 'lsmod' for loaded wireless modules, 'ip link show' or 'iwconfig' for wireless interfaces, and ensure the driver is actively managing a WiFi device.
    Affected if The WiFi driver is not loaded or the wireless interface is not active (the vulnerability requires the vulnerable driver code to be executing)

A system is affected if it contains a Mediatek WiFi chipset (Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628) running firmware version 7.6.2.3 with the 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply patch GN20220420013 to update the WiFi driver and remediate the missing bounds check. Verify all affected systems receive the driver update.

Fix this in Mt7603 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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