dbcve.org
YoctoApplication · Linuxfoundation

CVE-2022-32666

HIGH · 7.5 CVSS v3.1 Published 2023-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Wi-Fi, there is a possible low throughput due to misrepresentation of critical information. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220829014; Issue ID: GN20220829014.

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 vulnerability in Wi-Fi firmware allows remote attackers to cause denial of service via misrepresentation of critical information, leading to severely reduced network throughput. The flaw requires no authentication or user interaction to exploit.

MitigationApply vendor firmware patch GN20220829014. Until patch availability, network segmentation and monitoring for throughput anomalies may help detect exploitation.

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
YoctoApplication
Affected:= 4.0
Mt7603 FirmwareOperating system
Affected:= 7.6.6.0
Mt7613 FirmwareOperating system
Affected:= 7.6.6.0
Mt7615 FirmwareOperating system
Affected:= 7.6.6.0
Mt7622 FirmwareOperating system
Affected:= 7.6.6.0
Mt7628 FirmwareOperating system
Affected:= 7.6.6.0
Mt7629 FirmwareOperating system
Affected:= 7.6.6.0
Mt7915 FirmwareOperating system
Affected:= 7.6.6.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Mediatek Wi-Fi hardware in use
    Run `lspci | grep -i network` or `lspci | grep -i wireless` for PCIe Wi-Fi cards, or `lsusb` for USB adapters. For embedded devices, check `/proc/bus/pci` or board documentation.
    Affected if The system contains any of these chips: Mt7603, Mt7613, Mt7615, Mt7622, Mt7628, Mt7629, or Mt7915
  2. Retrieve Wi-Fi firmware version
    Check firmware version via `iw dev <interface> info`, `iw list`, or by reading firmware binary files in `/lib/firmware/mediatek/` directory. For embedded systems, use vendor-specific tools or check `/proc/mtd` for firmware partitions.
    Affected if The firmware version reported is exactly 7.6.6.0 for any affected Mediatek chipset
  3. Verify Linuxfoundation Yocto version if applicable
    If building custom firmware with Yocto, check the build configuration: examine `conf/local.conf` or run `bitbake -e | grep DISTRO_VERSION` in the build environment.
    Affected if The Yocto distribution version is exactly 4.0 and includes the affected Mediatek Wi-Fi firmware components
  4. Confirm Wi-Fi functionality is active
    Check that the Wi-Fi interface is up with `ip link show` or `ifconfig`, and verify network traffic is being handled by checking `iw dev <interface> link` or monitoring throughput.
    Affected if The vulnerable firmware is loaded and actively managing Wi-Fi connections
  5. Monitor for throughput degradation
    Baseline normal Wi-Fi throughput using `iperf3` or similar tools. Compare current throughput measurements against baseline. Look for severely reduced speeds despite normal signal strength.
    Affected if Network throughput is significantly lower than expected baseline without other explanatory causes

A system is affected if it runs Mediatek Wi-Fi firmware version 7.6.6.0 on any of the affected chipsets (Mt7603, Mt7613, Mt7615, Mt7622, Mt7628, Mt7629, Mt7915) or uses Yocto 4.0 with these firmware components, and the Wi-Fi functionality is actively enabled.

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 vendor firmware patch GN20220829014. Until patch availability, network segmentation and monitoring for throughput anomalies may help detect exploitation.

Fix this in Yocto Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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