LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26950: Out of bounds read in firmware for some Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products...

Out of bounds read in firmware for some Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products before version 22.120 may allow an authenticated user to potentially enable denial of service via local access.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-26950 is a denial-of-service risk in firmware for some Intel Wireless Bluetooth and Killer Bluetooth products before version 22.120. An authenticated local user could trigger an out-of-bounds read and disrupt availability. This is not presented as remote code execution or data theft.

Executive priority

Treat this as a moderate endpoint availability issue. It does not warrant emergency internet-facing incident response based on the provided evidence, but it should be included in normal endpoint driver and firmware patch cycles, especially for shared or high-availability workstations.

Technical view

The issue is CWE-125, an out-of-bounds read in Bluetooth firmware. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact. Affected products are listed broadly as some Intel Wireless Bluetooth and Killer Bluetooth products before 22.120.

Likely exposure

Exposure is most likely on laptops, desktops, or other managed endpoints using affected Intel Wireless Bluetooth or Killer Bluetooth firmware below version 22.120. Systems without those Bluetooth products, or already updated to 22.120 or later, are not indicated as affected by the provided sources.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked as KEV. Exploitation requires authenticated local access, which lowers internet-scale risk but matters on shared endpoints, unmanaged devices, or environments where local users can run code.

Researcher notes

Evidence is limited to the CVE record and Intel advisory reference. The affected range is broad and lacks specific model identifiers in the provided bundle. Validation should focus on product presence and firmware or package version, not generic Bluetooth availability alone.

Mitigation direction

  • Review Intel INTEL-SA-00628 for affected product details and update guidance.
  • Update affected Intel Wireless Bluetooth and Killer Bluetooth products to version 22.120 or later.
  • Prioritize managed endpoints with affected Bluetooth hardware and older firmware.
  • Track exceptions and revisit them against current Intel guidance.

Validation and detection

  • Inventory endpoints for Intel Wireless Bluetooth or Killer Bluetooth components.
  • Verify installed Bluetooth firmware or driver package versions are 22.120 or later.
  • Confirm affected systems are not relying on outdated OEM packages.
  • Document devices where vendor update guidance is unavailable or ambiguous.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-26950 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-26950Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aIntel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) productsbefore version 22.120Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.