CVE-2021-0165
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 in firmware for Intel(R) PROSet/Wireless Wi-Fi in multiple operating systems and Killer(TM) Wi-Fi in Windows 10 and 11 may allow an unauthenticated user to potentially enable denial of service via adjacent 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 Wi-Fi and Killer Wi-Fi firmware allows an unauthenticated attacker with adjacent network access to potentially cause denial of service by sending specially crafted wireless packets that trigger the validation failure.
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< 11.8.90< 11.8.90< 12.0.85< 12.0.85< 12.0.85>= 14.0.0, < 14.1.60>= 15.0.0, < 15.0.35>= 14.0.0, < 14.1.60>= 15.0.0, < 15.0.35< 15.0.35< 22.60CVSS 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 the installed Intel Wi-Fi adapter modelOpen Device Manager (devmgmt.msc), expand 'Network adapters', and look for Intel wireless adapters such as AC 8260, AC 8265, AC 9260, AC 9560, Wi-Fi 6 AX200, AX201, AX210, or AC 3165. Alternatively, run 'netsh wlan show interfaces' to list the wireless adapter.Affected if The system uses one of the Intel Wi-Fi adapter models listed in the affected products.
-
Check the firmware version of the Intel Wi-Fi adapterIn Device Manager, right-click the Intel wireless adapter, select Properties, go to the 'Driver' tab, and note the Driver Version. For more accurate firmware version, use Intel PROSet/Wireless software if installed, or Intel's PROSet/Wireless Adapter User Guide utility. The version format varies by adapter (for example, 11.x.x.x for older adapters or 12.x.x.x, 14.x.x.x, 15.x.x.x for Wi-Fi 6 adapters).Affected if The firmware version cannot be determined or is below the thresholds listed for your specific adapter model.
-
Compare against affected version ranges for AC 8260/8265If the adapter is AC 8260 or AC 8265, verify the firmware version is at least 11.8.90. Versions below 11.8.90 are affected.Affected if The installed firmware version is less than 11.8.90 for AC 8260 or AC 8265.
-
Compare against affected version ranges for AC 9260/9560If the adapter is AC 9260 or AC 9560, verify the firmware version is at least 12.0.85. Versions below 12.0.85 are affected.Affected if The installed firmware version is less than 12.0.85 for AC 9260 or AC 9560.
-
Compare against affected version ranges for Wi-Fi 6 adapters (AX200, AX201, AX210)For AX200, AX201, or AX210 adapters, check if the firmware version falls into any of these affected ranges: below 12.0.85, OR between 14.0.0 and 14.1.59 (inclusive), OR between 15.0.0 and 15.0.34 (inclusive). Note that AX200 also has the additional range below 12.0.85.Affected if The firmware version is less than 12.0.85, or is 14.0.0 to 14.1.59, or is 15.0.0 to 15.0.34 for AX200/AX201/AX210.
-
Compare against affected version ranges for AC 3165If the adapter is AC 3165, verify the firmware version is at least 22.60. Versions below 22.60 are affected.Affected if The installed firmware version is less than 22.60 for AC 3165.
A user is affected if their system has any of the listed Intel Wi-Fi adapters (8260, 8265, 9260, 9560, AX200, AX201, AX210, or 3165) with a firmware version that falls within the specific vulnerable ranges for that adapter model.
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 · scoped11.8.9012.0.8514.1.60
Apply Intel firmware updates or vendor-supplied patches for affected Wi-Fi adapters; prioritize systems with wireless exposure to adjacent attackers.
Upgrade to firmware version 11.8.90 (Amt Ac 8260/8265), 12.0.85 (Amt Ac 9260/9560, Amt Wi-Fi 6 Ax200), 14.1.60 (for 14.x branch), 15.0.35 (Amt Wi-Fi 6 Ax200/Ax201/Ax210), or 22.60 (Proset Ac 3165) as applicable to your specific adapter model
- 1. Identify the exact Intel Wi-Fi adapter model (e.g., AX200, AX201, AX210) in the affected system using Device Manager or system information utilities
- 2. Determine the current firmware version installed on the Wi-Fi adapter
- 3. Download the latest Intel Wi-Fi firmware update from the official Intel support website (www.intel.com) specific to the adapter model
- 4. Apply the firmware update using Intel's firmware update utility or the method specified in the product documentation
- 5. For Intel PROSet/Wireless users, ensure the wireless driver is also updated to a compatible version
- 6. Reboot the system after applying the firmware update
- 7. Verify the firmware has been updated to the fixed version: 11.8.90 or higher for AC 8260/8265, 12.0.85 or higher for AC 9260/9560 and AX200, 14.1.60 or higher for AX200/Ax201 (14.x branch), 15.0.35 or higher for AX200/Ax201/Ax210, or 22.60 or higher for Proset AC 3165
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0165 — 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-2021-0165 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