CVE-2021-0069
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 some Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10 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 · high confidenceImproper input validation in Intel PROSet/Wireless WiFi and Killer WiFi firmware allows an unauthenticated attacker within wireless range to potentially cause denial of service by sending specially crafted WiFi frames that the firmware processes without proper validation.
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< 22.40< 22.40< 22.40< 22.40< 22.40< 22.40all versions< 22.40CVSS 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 WiFi adapter modelOpen Device Manager on Windows, expand 'Network adapters', and look for Intel PROSet/Wireless or Killer WiFi adapter (e.g., Intel Wi-Fi 6 AX210, Intel Wi-Fi 6 AX201, etc.) or run 'netsh wlan show interfaces' to list wireless adapter detailsAffected if The adapter model matches one of the affected products: Ax210, Ax201, Ax200, Ac9560, Ac9462, Ac9461, 9260, or Ac9260
-
Retrieve the current firmware version of the WiFi adapterUse Intel PROSet Wireless tools (open Intel PROSet Wireless Software, go to Adapter Properties, view Firmware version) or run 'netsh wlan show drivers' and check driver/firmware details; on Linux, use 'iw list' or check /sys/class/net/*/device/firmware_versionAffected if The firmware version is visible and can be compared to the affected ranges
-
Compare installed firmware version against affected rangesReference the version retrieved in the previous step against: Ax210, Ax201, Ax200, Ac9560, Ac9462, Ac9461, Ac9260 all affected if < 22.40; Intel 9260 affected for all versionsAffected if The installed firmware version is below 22.40 (for Ax210, Ax201, Ax200, Ac9560, Ac9462, Ac9461, Ac9260) or any version (for Intel 9260)
-
Verify WiFi adapter is enabled and activeCheck that the wireless adapter is not disabled in BIOS/UEFI, and that WiFi is turned on in the operating system (check network status or use 'netsh wlan show interfaces' to confirm state is 'connected' or 'disconnected' but enabled)Affected if The WiFi adapter is powered on and capable of receiving wireless frames, which is required for the vulnerability to be exploitable
You are affected if your system uses any of the listed Intel WiFi adapters (Ax210, Ax201, Ax200, Ac9560, Ac9462, Ac9461, 9260, Ac9260) with firmware versions below 22.40 (or any version for 9260) and the wireless 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 · scoped22.40
Update WiFi adapter firmware to vendor-provided patches; apply vendor-released firmware updates for affected Intel PROSet/Wireless and Killer WiFi products.
Firmware version 22.40 or later for the respective Intel WiFi adapter (Ax210, Ax201, Ax200, AC9560, AC9462, AC9461, 9260, AC9260)
- Identify the specific Intel WiFi adapter model in the system (e.g., Ax210, Ax201, Ax200, AC9560, AC9462, AC9461, 9260, or AC9260)
- Download the latest Intel PROSet/Wireless WiFi driver and firmware package from the official Intel support website (www.intel.com)
- Ensure the system has adequate power (connected to AC power for laptops) to prevent interruption during the firmware update
- Run the Intel Driver & Support Assistant or manually install the updated wireless driver package, which includes the firmware update
- Restart the system after the firmware update completes to ensure the new firmware is properly loaded
- Verify the installed firmware version matches or exceeds 22.40 using Intel PROSet/Wireless tools or Device Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0069 — 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-0069 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