CVE-2022-26443
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: GN20220420068; Issue ID: GN20220420068.
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 confidenceA missing bounds check in a WiFi driver allows an out-of-bounds write vulnerability, enabling local privilege escalation to System level. The vulnerability requires the attacker to already have System execution privileges but does not require 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 adapterOn the target system, list network adapters and identify if any Mediatek wireless adapter is present (e.g., Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, Mt7628). On Windows, use 'netsh wlan show interfaces' or check Device Manager. On Linux, use 'lspci' or 'iwconfig'. On embedded devices, check '/proc/net/wireless' or vendor-specific commands.Affected if A Mediatek WiFi adapter matching the affected model list is present in the system
-
Retrieve WiFi firmware versionObtain the firmware version of the Mediatek WiFi adapter. On Windows, check driver properties in Device Manager or use 'wmic path win32_networkadapter get name, driverversion'. On Linux, check via 'ethtool -i wlan0' or firmware loading logs in 'dmesg'. On embedded devices, check vendor-specific interfaces or firmware version files.Affected if The firmware version returned is exactly 7.6.2.3
-
Verify driver version matches affected buildCross-reference the retrieved WiFi driver/firmware version against the affected version 7.6.2.3. Confirm whether the exact version string matches (note: version comparison should treat '=' as exact match per the affected products list).Affected if The installed WiFi firmware version equals 7.6.2.3 exactly
The system is affected if it contains any of the listed Mediatek WiFi adapters (Mt7603, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, Mt7628) running firmware version exactly 7.6.2.3, and the attacker already has System-level execution privileges to trigger the privilege escalation.
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 patch GN20220420068 or update the WiFi driver to the patched version that includes the bounds checking fix.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26443 — 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-26443 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