dbcve.org
Ax211 FirmwareOperating system · Intel

CVE-2021-33155

MEDIUM · 5.7 CVSS v3.1 Published 2022-02-09
Fix available
A fix is available. Upgrade to 22.100 or later.
See remediation →
59/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper input validation in firmware for some Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products before version 22.100 may allow an authenticated 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 confidence

Improper input validation in the firmware of Intel Wireless Bluetooth and Killer Bluetooth products before version 22.100 allows an authenticated adjacent user (within Bluetooth range) to potentially cause denial of service. The vulnerability is exploitable via adjacent access and requires authentication, which in Bluetooth context means a paired/connected device.

MitigationUpdate Bluetooth firmware to version 22.100 or later on affected Intel and Killer wireless adapters.

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
Ax211 FirmwareOperating system
Affected:< 22.100
Ax210 FirmwareOperating system
Affected:< 22.100
Ax201 FirmwareOperating system
Affected:< 22.100
Ax200 FirmwareOperating system
Affected:< 22.100
Ac 9560 FirmwareOperating system
Affected:< 22.100
Ac 9462 FirmwareOperating system
Affected:< 22.100
Ac 9461 FirmwareOperating system
Affected:< 22.100
Ac 9260 FirmwareOperating system
Affected:< 22.100

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Bluetooth adapter model
    On Windows, open Device Manager and expand 'Bluetooth' to see the adapter name (e.g., Intel Wi-Fi 6 AX211, Killer Bluetooth). On Linux, run 'lspci' or check 'hciconfig -a' output for the adapter name.
    Affected if The adapter is any of: Intel AX211, AX210, AX201, AX200, AC9560, AC9462, AC9461, AC9260, or corresponding Killer variants.
  2. Check the Bluetooth firmware version
    On Windows, open Device Manager, right-click the Bluetooth adapter, select Properties, go to the 'Driver' or 'Firmware' tab to view the firmware version. Alternatively, use the Intel Driver & Support Assistant or 'fwts' on Linux to query firmware version.
    Affected if The displayed firmware version is below 22.100 (e.g., 22.50, 21.0, etc.).
  3. Verify if Bluetooth is enabled and actively used
    Check system Bluetooth settings to confirm Bluetooth is turned on. Review paired Bluetooth devices list to confirm at least one device is paired or connected.
    Affected if Bluetooth is enabled and has paired/connected devices, as the vulnerability requires an authenticated adjacent attacker (paired device) to exploit.
  4. Confirm the adapter uses vulnerable firmware
    Cross-reference the identified adapter model and firmware version against the affected versions: Intel AX211, AX210, AX201, AX200, AC9560, AC9462, AC9461, AC9260 all versions prior to 22.100.
    Affected if The adapter is one of the listed models AND the firmware version is less than 22.100.

You are affected if you have an Intel AX200/AX201/AX210/AX211 or AC9260/AC9461/AC9462/AC9560 adapter (or Killer equivalent) with Bluetooth firmware version below 22.100, and Bluetooth is enabled with paired devices.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 22.100 or later
Fixed in 22.100
Interim mitigation

Update Bluetooth firmware to version 22.100 or later on affected Intel and Killer wireless adapters.

Recommended fix High confidence

Firmware version 22.100 or later for Intel Wireless Bluetooth and Killer Bluetooth adapters (Ax211, Ax210, Ax201, Ax200, Ac 9560, Ac 9462, Ac 9461, Ac 9260)

  1. Identify the exact Wi-Fi/Bluetooth adapter model (e.g., AX210, AX200, AC9560) using device manager or system information
  2. Determine the current firmware version installed on the adapter
  3. Download the latest Intel Wireless Bluetooth firmware package from intel.com or the system manufacturer's support site
  4. Run the firmware update utility provided by Intel or the original equipment manufacturer
  5. Follow the on-screen prompts to update the Bluetooth firmware to version 22.100 or later
  6. Verify the firmware has been successfully updated by checking the version in device manager after reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ax211 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33155 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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