Threats / Qualcomm / CVE-2021-1906
CVE-2021-1906
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
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-035EPSS 0.0052 (verify live)6CVSS 6.23CISA SSVC Exploitation: active · Automatable: no · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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).
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
CVSS 6.2 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) · Affected: Qualcomm, Multiple Chipsets. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-390 CWE-390.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 180 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
WeaknessCWE-390 · CWE-390
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by qualcommCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.