CVE-2022-32663
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 Wi-Fi driver, there is a possible system crash due to null pointer dereference. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220720014; Issue ID: GN20220720014.
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 · high confidenceA null pointer dereference vulnerability exists in a Wi-Fi driver that can be triggered remotely, causing a system crash and leading to denial of service. The vulnerability requires no user interaction or elevated privileges to exploit.
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= 7.6.6.1= 7.6.6.1= 7.6.6.1= 7.6.6.1= 7.6.6.1= 7.6.6.1= 7.6.6.1= 7.6.6.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mediatek Wi-Fi chipset in useCheck device documentation, FCC labeling, or use commands like 'lspci', 'lsusb', or 'iw list' to identify the wireless chipset modelAffected if Device uses any of: Mt5221, Mt7603, Mt7613, Mt7615, Mt7622, Mt7628, Mt7629, or Mt7668 chipsets
-
Check Wi-Fi driver or firmware versionUse vendor-specific commands or check /proc/mt_wifi or similar debugfs entries, or retrieve firmware version via 'cat /sys/class/net/wlan*/device/firmware_version' or 'mtkdiag' tool if availableAffected if Firmware version is exactly 7.6.6.1 on any affected chipset
-
Confirm Wi-Fi interface is activeCheck with 'ip link show' or 'ifconfig' for active wlan interfaces, or verify radio is enabled via 'iw dev' or wireless configuration UIAffected if Wi-Fi radio is enabled and interface is up - the vulnerability exists in the Wi-Fi driver code path when active
-
Monitor for Wi-Fi subsystem crashesCheck kernel logs via 'dmesg', 'journalctl -k', or /var/log/messages for NULL pointer dereference errors, kernel panics, or Wi-Fi driver fault messages occurring via remote Wi-Fi framesAffected if Unexpected Wi-Fi driver crashes, system reboots correlating with Wi-Fi traffic, or NULL pointer dereference errors in wireless driver logs appear
Device is affected if it runs any of the listed Mediatek chipsets with Wi-Fi enabled and firmware version exactly 7.6.6.1, or if unexplained Wi-Fi driver crashes are observed in logs.
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 GN20220720014 to update the affected Wi-Fi driver. Until the patch is applied, network segmentation and monitoring for anomalous Wi-Fi driver behavior can help detect exploitation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32663 — 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-2022-32663 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