Skip to content
Fencer Vulns
medium 6.5

CVE-2021-33110 json

Improper input validation for some Intel(R) Wireless Bluetooth(R) products and Killer(TM) Bluetooth(R) products in Windows 10 and 11 before…

published 2022-02-09 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-19825

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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.

Patch / fix

  • intel ac_1550_firmware 22.80
  • intel ac_3165_firmware 22.80
  • intel ac_3168_firmware 22.80
  • intel ac_7265_firmware 22.80
  • intel ac_8260_firmware 22.80
  • intel ac_8265_firmware 22.80
  • intel ac_9260_firmware 22.80
  • intel ac_9461_firmware 22.80
  • intel ac_9462_firmware 22.80
  • intel ac_9560_firmware 22.80
  • intel ax1650_firmware 22.80
  • intel ax1675_firmware 22.80
  • intel ax200_firmware 22.80
  • intel ax201_firmware 22.80
  • intel ax210_firmware 22.80

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 3.3 AV:A/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • n/a Intel(R) Wireless Bluetooth(R) products and Killer(TM) Bluetooth(R) products in Windows 10 and 11

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.