LiveActive security incident?Get immediate response
CVE Record

CVE-2021-1906: Improper handling of address deregistration on failure can lead to new GPU address allocation failure.

Improper handling of address deregistration on failure can lead to new GPU address allocation failure. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

MediumCVSS 6.2Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Qualcomm Snapdragon GPU availability issue. A local attacker could trigger a failure path that stops new GPU address allocations, potentially disrupting device functionality. The technical CVSS score is medium, but CISA KEV listing means exploitation has been observed and affected fleets should not treat it as theoretical.

Executive priority

Prioritize remediation where affected Qualcomm-based devices are managed business assets or operational technology. KEV status raises urgency, even though the vulnerability mainly affects availability and requires local attack conditions.

Technical view

CVE-2021-1906 involves improper handling of address deregistration after failure in Qualcomm Snapdragon products. The CVSS vector is local, low complexity, no privileges, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact. The bundle names broad Snapdragon product families and many chip identifiers.

Likely exposure

Exposure is most likely in Android, embedded, automotive, IoT, wearable, connectivity, and compute devices using affected Qualcomm Snapdragon components. Actual risk depends on the device model, OEM firmware branch, and whether the May 2021 Qualcomm fixes reached that product.

Exploitation context

CISA lists CVE-2021-1906 in the Known Exploited Vulnerabilities catalog, supporting active exploitation. The provided sources do not describe exploit mechanics, affected campaigns, or whether exploitation is targeted or widespread. The CVSS vector indicates local access is required.

Researcher notes

The source bundle does not name a CWE, exploit technique, or patch identifiers beyond Qualcomm’s bulletin. Analysis should stay tied to chip and firmware mapping. Avoid assuming all Snapdragon-branded devices are vulnerable without matching the listed components and OEM update status.

Mitigation direction

  • Inventory devices using affected Qualcomm Snapdragon components.
  • Check Qualcomm and OEM advisories for fixed firmware availability.
  • Apply OEM firmware or security updates that include the May 2021 Qualcomm fixes.
  • Prioritize unsupported or stale mobile, IoT, automotive, and embedded deployments.
  • Use CISA KEV status to drive remediation timelines.

Validation and detection

  • Map device models to Qualcomm chip identifiers listed in the advisory.
  • Confirm installed firmware security patch level with OEM documentation.
  • Verify whether the OEM update includes Qualcomm May 2021 bulletin fixes.
  • Track exceptions where no vendor patch is available.
  • Monitor endpoint stability and GPU-related crash telemetry after remediation.
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.

cve · low confidence lookup

CVE-2021-1906 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
6.2 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/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
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:N/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
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon WearablesAPQ8009, APQ8009W, APQ8017, APQ8053, APQ8064AU, APQ8096AU, AQT1000, AR8031, AR8035, AR8151, CSRA6620, CSRA6640, CSRB31024, FSM10055, FSM10056, MDM9150, MDM9206, MDM9250, MDM9607, MDM9626, MDM9628, MDM9650, MSM8909W, MSM8917, MSM8953, MSM8996AU, PM215, PM3003A, PM4125, PM4250, PM439, PM456, PM6125, PM6150, PM6150A, PM6150L, PM6250, PM6350, PM640A, PM640L, PM640P, PM660, PM660A, PM660L, PM670, PM670A, PM670L, PM7150A, PM7150L, PM7250, PM7250B, PM7350C, PM8004, PM8005, PM8008, PM8009, PM8150, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM8350, PM8350B, PM8350BH, PM8350BHS, PM8350C, PM855, PM855A, PM855B, PM855L, PM855P, PM8909, PM8916, PM8937, PM8953, PM8998, PMC1000H, PMD9607, PMD9655, PMD9655AU, PME605, PMI632, PMI8937, PMI8952, PMI8998, PMK7350, PMK8002, PMK8003, PMK8350, PMM6155AU, PMM8155AU, PMM8195AU, PMM855AU, PMM8996AU, PMR525, PMR735A, PMR735B, PMX20, PMX24, PMX50, PMX55, QAT3514, QAT3516, QAT3518, QAT3519, QAT3522, QAT3550, QAT3555, QAT5515, QAT5516, QAT5522, QAT5533, QAT5568, QBT1000, ...[truncated*]Listed
Weakness

CWE details

No CWE listed

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