basicsecurity.net
Proof, not just disclosure.
Threats / Qualcomm / CVE-2021-1906
CVE-2021-1906 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Qualcomm Multiple Chipsets vulnerability

Multiple Qualcomm chipsets contain an error handling vulnerability in GPU address deregistration that can lead to allocation failures, potentially causing denial of service or system instability.

Verdict

Today item — known-exploited.

A detection of error condition without action flaw in Qualcomm chipsets allows improper handling of GPU address deregistration on failure, resulting in new GPU address allocation failures that could degrade system functionality or enable denial of service.

CISA KEV Yes · 2021-11-033EPSS 0.0052 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.0052 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Qualcomm, Multiple Chipsets. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-390 CWE-390.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I trigger a GPU address deregistration failure through crafted operations or resource exhaustion.
Business
System experiences GPU memory allocation failures, reducing graphics performance and application responsiveness.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the unhandled error condition to prevent proper cleanup of GPU address space.
Business
Device stability degrades as GPU resources become unavailable for legitimate workloads.
3

Lateral reach — past segmentation narrative 3

Attacker
I repeatedly trigger allocation failures to exhaust available GPU address space.
Business
End users experience system hangs, application crashes, or complete loss of graphics functionality.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by qualcomm (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by qualcommCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.