LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11309: Use after free in GPU driver while mapping the user memory to GPU memory due to improper check of reference...

Use after free in GPU driver while mapping the user memory to GPU memory due to improper check of referenced memory in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11309 is a Qualcomm Snapdragon GPU driver memory-safety flaw. The issue can occur while mapping user memory into GPU memory, creating a use-after-free condition. The public bundle does not provide severity scoring, exploitability details, or confirmed remediation status.

Executive priority

Treat this as an exposure-management item rather than a confirmed emergency. The broad Snapdragon footprint matters, but urgency cannot be ranked confidently without vendor patch status, CVSS data, or exploitation evidence.

Technical view

The CVE describes a use-after-free in the GPU driver caused by improper checking of referenced memory during user-to-GPU memory mapping. Affected product families include Snapdragon Auto, Compute, Connectivity, Consumer IoT, Industrial IoT, Mobile, Voice & Music, and Wearables, with many Qualcomm part numbers listed.

Likely exposure

Exposure is most likely in devices using affected Qualcomm Snapdragon platforms and vulnerable GPU driver firmware. Risk depends on the exact chipset, device vendor integration, and installed OEM security update level.

Exploitation context

The provided sources do not show CISA KEV listing or any cited active exploitation. No exploit method, attacker requirements, privilege level, or impact scope is included in the source bundle.

Researcher notes

The source bundle lacks CVSS, CWE, exploit status, and concrete fix details. Researchers should focus on Qualcomm/OEM advisory correlation, affected chipset mapping, and update-level verification rather than assuming universal exploitability.

Mitigation direction

  • Review Qualcomm March 2021 bulletin and OEM advisories for affected device guidance.
  • Apply vendor-approved firmware, driver, or security updates when available.
  • Inventory Qualcomm Snapdragon-based devices across mobile, IoT, automotive, and embedded fleets.
  • Prioritize unsupported or rarely updated devices for replacement or compensating controls.

Validation and detection

  • Map device models to Qualcomm chipsets and part numbers listed in the CVE record.
  • Check installed Android, firmware, or BSP security patch levels against OEM guidance.
  • Confirm whether the device uses an affected Snapdragon platform and GPU driver stack.
  • Track remediation evidence from OEM release notes, MDM inventory, or asset records.
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-2020-11309 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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, MDM9206, 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, PM8996, PM8998, PMC1000H, PMD9607, PMD9655, PME605, PMI632, PMI8937, PMI8952, PMI8994, PMI8996, PMI8998, PMK7350, PMK8001, PMK8002, PMK8003, PMK8350, PMM6155AU, PMM8155AU, PMM8195AU, PMM855AU, PMM8996AU, PMR525, PMR735A, PMR735B, PMW3100, PMX20, PMX24, PMX50, PMX55, QAT3514, QAT3516, QAT3518, QAT3519, QAT3522, QAT3550, QAT3555, QAT5515, QAT5516, QAT5522, QAT5533, QAT ...[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.