CVE-2021-0175
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 Validation of Specified Index, Position, or Offset in Input in firmware for some Intel(R) PROSet/Wireless Wi-Fi in multiple operating systems and some 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 confidenceA vulnerability in Intel PROSet/Wireless Wi-Fi and Killer Wi-Fi firmware allows improper validation of specified index, position, or offset values in input handling. An unauthenticated attacker within adjacent network range can send specially crafted packets to trigger a denial of service condition, causing the Wi-Fi adapter to become unresponsive or crash.
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 Wi-Fi adapter modelOn Windows, open Device Manager > Network adapters. Look for Intel PROSet, Intel Wireless, or Killer Wi-Fi adapter entries (e.g., Intel Wi-Fi 6 AX200, Killer Wi-Fi 6 AX1650). On Linux, run 'lspci | grep -i wireless' or 'lspci | grep -i network'. Record the exact model name.Affected if The adapter model matches any of these: AC 8260, AC 8265, AC 9260, AC 9560, Wi-Fi 6 AX200, Wi-Fi 6 AX201, Wi-Fi 6 AX210, or AC 3165.
-
Locate firmware versionOn Windows, open Intel PROSet Wireless software or use Intel Driver & Support Assistant. The firmware version is listed under adapter properties or firmware details. On Linux, use 'iw list' or check /lib/firmware/ for the iwlwifi driver files, or run 'ethtool -i wlan0'. Record the firmware version string.Affected if A firmware version is installed but cannot be determined or is below the safe versions.
-
Compare version against affected rangesCompare your installed firmware version to the following safe versions: AC 8260/8265 need >= 11.8.90; AC 9260/9560 need >= 12.0.85; AX200 needs >= 12.0.85 AND >= 14.1.60 AND >= 15.0.35; AX201 needs >= 14.1.60 AND >= 15.0.35; AX210 needs >= 15.0.35; AC 3165 needs >= 22.60.Affected if Your installed firmware version falls within any of these vulnerable ranges: AC 8260/8265 < 11.8.90; AC 9260/9560 < 12.0.85; AX200 < 12.0.85 OR (>= 14.0.0 AND < 14.1.60) OR (>= 15.0.0 AND < 15.0.35); AX201 (>= 14.0.0 AND < 14.1.60) OR (>= 15.0.0 AND < 15.0.35); AX210 < 15.0.35; AC 3165 < 22.60.
-
Verify Wi-Fi interface is activeOn Windows, check if Wi-Fi adapter shows as enabled in Network Connections. On Linux, run 'ip link show' or 'iwconfig' to confirm the wireless interface (e.g., wlan0) is up. The vulnerability requires the adapter to be powered on and in range.Affected if The Wi-Fi adapter is enabled and actively scanning or connected to a network, making it reachable by adjacent attackers.
You are affected if your system uses one of the listed Intel or Killer Wi-Fi adapter models with firmware versions below the safe thresholds and the Wi-Fi adapter is enabled.
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 firmware updates provided by Intel or Killer for the affected Wi-Fi adapters. As a defensive measure, limit exposure by restricting physical/proximity access to trusted networks and monitor for unexpected Wi-Fi adapter failures.
Upgrade to firmware version 11.8.90 (for 8260/8265), 12.0.85 (for 9260/9560), 15.0.35 (for AX200/AX201/AX210), or 22.60 (for 3165)
- Identify the exact wireless adapter model in the system (e.g., AX200, AX210, 8260, etc.)
- Determine the current firmware version installed on the wireless adapter
- Download the latest firmware update from Intel's support website or through the Intel PROSet/Wireless driver package
- Apply the firmware update using Intel's firmware update utility or driver package installation
- Reboot the system after applying the firmware update
- Verify the firmware version has been updated to a fixed release (11.8.90, 12.0.85, 15.0.35, or 22.60 depending on adapter model)
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2021-0175 — 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-0175 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