CVE-2021-33110

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.

Published: 2022-02-09 Last update: 2025-05-05 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-33110 is rated Moderate Risk (44.6/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.30%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-33110

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-06 0.40% 0.30% -0.10%
2 2025-11-21 0.15% 0.40% +0.25%
3 2025-11-18 — 0.15% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-33110

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0
3.3 2.0 LOW
AV:A/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 6.5 2.9 [email protected]

Weakness enumeration for CVE-2021-33110

OS Trackers for CVE-2021-33110

vendor priority summary link
ubuntu medium CVE-2021-33110 medium priority: Ubuntu including 1 source packages (linux-firmware), 14 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 6. https://ubuntu.com/security/CVE-2021-33110

Affected software / configurations for CVE-2021-33110

Vendor Product Version Raw CPE
intel ac_1550_firmware < 22.80 cpe:2.3:o:intel:ac_1550_firmware:*:*:*:*:*:*:*:*
intel ac_3165_firmware < 22.80 cpe:2.3:o:intel:ac_3165_firmware:*:*:*:*:*:*:*:*
intel ac_3168_firmware < 22.80 cpe:2.3:o:intel:ac_3168_firmware:*:*:*:*:*:*:*:*
intel ac_7265_firmware < 22.80 cpe:2.3:o:intel:ac_7265_firmware:*:*:*:*:*:*:*:*
intel ac_8260_firmware < 22.80 cpe:2.3:o:intel:ac_8260_firmware:*:*:*:*:*:*:*:*
intel ac_8265_firmware < 22.80 cpe:2.3:o:intel:ac_8265_firmware:*:*:*:*:*:*:*:*
intel ac_9260_firmware < 22.80 cpe:2.3:o:intel:ac_9260_firmware:*:*:*:*:*:*:*:*
intel ac_9461_firmware < 22.80 cpe:2.3:o:intel:ac_9461_firmware:*:*:*:*:*:*:*:*
intel ac_9462_firmware < 22.80 cpe:2.3:o:intel:ac_9462_firmware:*:*:*:*:*:*:*:*
intel ac_9560_firmware < 22.80 cpe:2.3:o:intel:ac_9560_firmware:*:*:*:*:*:*:*:*
intel ax1650_firmware < 22.80 cpe:2.3:o:intel:ax1650_firmware:*:*:*:*:*:*:*:*
intel ax1675_firmware < 22.80 cpe:2.3:o:intel:ax1675_firmware:*:*:*:*:*:*:*:*
intel ax200_firmware < 22.80 cpe:2.3:o:intel:ax200_firmware:*:*:*:*:*:*:*:*
intel ax201_firmware < 22.80 cpe:2.3:o:intel:ax201_firmware:*:*:*:*:*:*:*:*
intel ax210_firmware < 22.80 cpe:2.3:o:intel:ax210_firmware:*:*:*:*:*:*:*:*

References for CVE-2021-33110

cvelogic Threat Intelligence