CVE-2022-26047
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 · uneditedImproper input validation for some Intel(R) PROSet/Wireless WiFi, Intel vPro(R) CSME WiFi and Killer(TM) WiFi products may allow unauthenticated user to potentially enable denial of service via local access.
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 confidenceImproper input validation in Intel PROSet/Wireless WiFi, Intel vPro CSME WiFi, and Killer WiFi drivers allows an unauthenticated local attacker to trigger a denial of service condition. The vulnerability stems from insufficient validation of input data processed by the WiFi software components.
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< 3.1122.3158< 22.140< 2.2.14.22176all versionsall versionsall versionsall versionsall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 installed Intel PROSet/Wireless WiFi software versionOpen Windows Control Panel > Programs and Features, or use 'wmic product get name,version' to list installed Intel WiFi softwareAffected if Version is present and less than 22.140
-
Identify installed Killer WiFi software versionOpen Windows Control Panel > Programs and Features, or check the Killer Support Center app for software version informationAffected if Version is present and less than 3.1122.3158
-
Identify WiFi adapter firmware versionOpen Device Manager > Network Adapters > right-click WiFi adapter > Properties > Driver tab, or use 'netsh wlan show interfaces' to display firmware detailsAffected if Adapter model is one of: Killer WiFi 6 Ax1650, Killer WiFi 6e Ax1675, Killer WiFi 6e Ax1690, WiFi 6 Ax200, or WiFi 6 Ax201 (all firmware versions affected)
-
Check Intel UEFI WiFi Driver versionOpen Device Manager > System Devices > Intel UEFI WiFi Driver (if present) and check driver version in Properties, or check BIOS/UEFI firmware version if the driver is bundledAffected if Driver version is present and less than 2.2.14.22176
You are affected if any Intel PROSet/Wireless WiFi software is below 22.140, any Killer WiFi software is below 3.1122.3158, the Intel UEFI WiFi Driver is below 2.2.14.22176, or your adapter uses any firmware version on the Killer WiFi 6 Ax1650/6e Ax1675/6e Ax1690 or WiFi 6 Ax200/Ax201 models.
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.
dbcve · scoped2.2.14.221763.1122.315822.140
Apply vendor-supplied patches or firmware updates for affected Intel and Killer WiFi products. Until patches are available, limit physical and local access to systems with vulnerable WiFi components.
Killer Wifi Software: 3.1122.3158 | Intel PROSet/Wireless WiFi: 22.140 | UEFI WiFi Driver: 2.2.14.22176 | Respective firmware updates from Intel/system manufacturer
- Identify the specific Killer or Intel WiFi product and current version installed on the system
- For Killer Wifi Software: Navigate to the Killer Support website or use the Killer Intelligence Center to check for updates and upgrade to version 3.1122.3158 or later
- For Intel PROSet/Wireless WiFi: Use Intel Driver & Support Assistant or manually download from Intel support to upgrade to version 22.140 or later
- For UEFI WiFi Driver: Obtain the updated driver version 2.2.14.22176 or later from the system manufacturer or Intel
- For firmware versions listed as 'all versions' affected (Ax1650, Ax1675, Ax1690, Ax200, Ax201): Contact the system manufacturer or Intel for firmware updates that address the vulnerability
- Verify the update was successful by checking the installed version number after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26047 — 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-26047 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