dbcve.org
Ac 1550 FirmwareOperating system · Intel

CVE-2021-33110

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-09
Fix available
A fix is available. Upgrade to 22.80 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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 for some Intel(R) Wireless Bluetooth(R) products and Killer(TM) Bluetooth(R) products in Windows 10 and 11 before version 22.80 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 confidence

Improper input validation in Intel Wireless Bluetooth and Killer Bluetooth drivers for Windows 10/11 before version 22.80 allows an unauthenticated attacker within adjacent range to cause a denial of service via malformed Bluetooth input.

MitigationUpdate Bluetooth drivers to version 22.80 or later through vendor-supplied updates or Windows Update.

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
Ac 1550 FirmwareOperating system
Affected:< 22.80
Ac 3165 FirmwareOperating system
Affected:< 22.80
Ac 3168 FirmwareOperating system
Affected:< 22.80
Ac 7265 FirmwareOperating system
Affected:< 22.80
Ac 8260 FirmwareOperating system
Affected:< 22.80
Ac 8265 FirmwareOperating system
Affected:< 22.80
Ac 9260 FirmwareOperating system
Affected:< 22.80
Ac 9461 FirmwareOperating system
Affected:< 22.80

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
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 checks

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

  1. Identify Intel Bluetooth hardware
    Open Device Manager, expand 'Bluetooth', and look for Intel wireless adapters (such as Intel AC 1550, 3165, 3168, 7265, 8260, 8265, 9260, or 9461). Alternatively, run 'Get-PnpDevice -Class Bluetooth' in PowerShell and note the friendly name.
    Affected if No Intel Bluetooth adapter is present - the system is not affected by this specific CVE.
  2. Check Bluetooth firmware version
    In Device Manager, right-click the Intel Bluetooth device, select 'Properties', go to the 'Firmware' tab, and note the firmware version. Alternatively, use 'Get-ItemProperty' on the driver registry key at 'HKLM:\SYSTEM\CurrentControlSet\Services\BthUSB\Parameters\General' or the Intel driver utility if installed.
    Affected if Firmware version is lower than 22.80 - the system is potentially affected.
  3. Confirm driver version matches Intel range
    Cross-reference the firmware version against the list of affected products: Intel AC 1550, 3165, 3168, 7265, 8260, 8265, 9260, 9461 with firmware versions below 22.80.
    Affected if The adapter is one of the affected models and version is below 22.80 - the system is affected.
  4. Verify Bluetooth is enabled
    Check if Bluetooth is turned on in Windows Settings > Devices > Bluetooth & other devices, or run 'Get-PnpDevice -Class Bluetooth | Where-Object {$_.Status -eq "OK"}' in PowerShell.
    Affected if Bluetooth is disabled - the attack surface is not present though the vulnerable firmware still exists.

A user is affected if their system has an Intel wireless Bluetooth adapter from the listed models with firmware version below 22.80 and has Bluetooth enabled.

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.80 or later
Fixed in 22.80
Interim mitigation

Update Bluetooth drivers to version 22.80 or later through vendor-supplied updates or Windows Update.

Recommended fix High confidence

Intel Wireless Bluetooth Firmware version 22.80 or later for the specific adapter (AC 1550, 3165, 3168, 7265, 8260, 8265, 9260, or 9461)

  1. Identify the specific Intel wireless Bluetooth adapter model in the system (e.g., AC 8265, AC 9260)
  2. Download the Intel Wireless Bluetooth driver/firmware package version 22.80 or later from Intel's official support website for the specific adapter model
  3. Extract and run the Intel driver installation utility
  4. Follow the on-screen prompts to update the Bluetooth driver and firmware
  5. Restart the computer to complete the firmware update
  6. Verify the installed firmware version is 22.80 or higher using Intel's driver details or Windows Device Manager
Caveat Standard firmware update - minimal risk; ensure system has adequate power during update to prevent brick

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

Fix this in Ac 1550 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33110 — 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-33110 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