CVE-2022-26444
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 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: GN20220420075; Issue ID: GN20220420075.
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 missing bounds check in the wifi driver allows an out-of-bounds write, enabling a local attacker to escalate privileges to System level without user interaction.
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.2.3= 7.6.2.3= 7.6.2.3= 7.6.2.3= 7.6.2.3= 7.6.2.3= 7.6.2.3= 7.6.2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mediatek WiFi hardware in the systemReview system hardware information, device specifications, or network adapter details to determine if a Mediatek wireless chip (Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628) is presentAffected if The system does not contain one of the listed Mediatek chip models, then it is not affected by this specific CVE
-
Determine the installed WiFi firmware versionAccess the firmware version information for the Mediatek wireless chip through device management interfaces, firmware utilities, or system logs that report wireless adapter detailsAffected if The firmware version is exactly 7.6.2.3 for the identified Mediatek chip model, then it matches the affected version listed in the CVE
-
Verify the WiFi driver is loaded and activeCheck system status to confirm the wireless adapter and its driver are currently enabled and runningAffected if The WiFi driver is not loaded or the wireless interface is disabled, the exploitation vector may not be reachable, though the vulnerable firmware version still poses a risk if re-enabled
A system is affected if it contains a Mediatek Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628 WiFi chip running firmware version exactly 7.6.2.3 with the wireless driver active.
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 GN20220420075 to add proper bounds validation in the wifi driver memory handling routine.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26444 — 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-26444 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