LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11230: Potential arbitrary memory corruption when the qseecom driver updates ion physical addresses in the buffer...

Potential arbitrary memory corruption when the qseecom driver updates ion physical addresses in the buffer as it exposes a physical address to user land in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11230 is a Qualcomm Snapdragon driver issue that may allow arbitrary memory corruption. The public bundle says the qseecom driver can expose a physical memory address to user land while updating ION buffer addresses. Business risk depends on whether affected Snapdragon components are present in managed products or fleets.

Executive priority

Treat this as an inventory-and-patching priority for Qualcomm-based products, not as a confirmed emergency. The impact class is serious, but public severity, exploitation, and fix details are incomplete in the provided sources.

Technical view

The issue is in Qualcomm’s qseecom driver logic for updating ION physical addresses in a buffer. The CVE description says this exposes a physical address to user land and can cause potential arbitrary memory corruption across listed Snapdragon Auto, Compute, Connectivity, Industrial IoT, and Mobile components.

Likely exposure

Exposure is limited to systems using the affected Qualcomm Snapdragon product families and component list. The bundle does not identify specific phones, vehicles, IoT devices, operating system builds, or OEM firmware versions, so asset mapping is required.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. It also does not provide exploit prerequisites, required privileges, attack vector, or real-world exploitation reports.

Researcher notes

Key missing details include CVSS, CWE, attack vector, privilege requirements, affected firmware ranges, and patch identifiers. Analysis should stay anchored to Qualcomm’s advisory and OEM downstream bulletins rather than assuming device-specific exposure.

Mitigation direction

  • Check Qualcomm’s March 2021 bulletin and affected OEM advisories for CVE-2020-11230 guidance.
  • Inventory Snapdragon Auto, Compute, Connectivity, Industrial IoT, and Mobile components in supported products.
  • Apply vendor or OEM firmware updates that explicitly address CVE-2020-11230.
  • Prioritize managed mobile, embedded, IoT, and automotive systems using affected Qualcomm components.
  • Monitor Qualcomm and OEM security bulletins for later clarification or superseding fixes.

Validation and detection

  • Map hardware bills of materials against Qualcomm’s affected component list.
  • Confirm each affected product’s OEM advisory references CVE-2020-11230 or Qualcomm’s March 2021 bulletin.
  • Verify deployed firmware or OS security level after vendor remediation.
  • Record devices where OEM support status or patch availability is unclear.
  • Track exceptions for unsupported devices pending replacement or compensating controls.
Prepared
Confidence
medium
Sources
3

Public sources used

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-11230 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon MobileAQT1000, FSM10055, PM3003A, PM7150A, PM7150L, PM7250, PM7250B, PM7350C, PM8004, PM8008, PM8009, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM8350, PM8350B, PM8350BH, PM8350BHS, PM8350C, PM855, PM855A, PM855B, PM855L, PM855P, PMK7350, PMK8002, PMK8350, PMM6155AU, PMM8155AU, PMM8195AU, PMR525, PMR735A, PMR735B, PMX50, PMX55, QAT3514, QAT3516, QAT3518, QAT3519, QAT3555, QAT5515, QAT5516, QAT5522, QAT5533, QAT5568, QBT2000, QCA6390, QCA6391, QCA6420, QCA6421, QCA6426, QCA6430, QCA6431, QCA6436, QCA6574AU, QCA6696, QDM2301, QDM2305, QDM2307, QDM2308, QDM2310, QDM3301, QDM3302, QDM4643, QDM4650, QDM5579, QDM5620, QDM5621, QDM5650, QDM5652, QDM5670, QDM5671, QDM5677, QDM5679, QET4101, QET5100, QET5100M, QET6100, QET6110, QFS2530, QFS2580, QFS2608, QFS2630, QLN4642, QLN4650, QLN5020, QLN5030, QLN5040, QPA2625, QPA5461, QPA5580, QPA5581, QPA6560, QPA8673, QPA8686, QPA8801, QPA8802, QPA8803, QPA8821, QPA8842, QPM4621, QPM4630, QPM4640, QPM4641, QPM4650, QPM5621, QPM5641, QPM5658, QPM5670, QPM5677, QPM5 ...[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.