LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11220: While processing storage SCM commands there is a time of check or time of use window where a pointer used c...

While processing storage SCM commands there is a time of check or time of use window where a pointer used could be invalid at a specific time while executing the storage SCM call in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11220 is a Qualcomm Snapdragon vulnerability in storage SCM command handling. A timing issue could leave a pointer invalid while the storage call is running. The sources identify many Snapdragon product families, but do not provide severity, impact, CVSS, or exploit detail.

Executive priority

Treat this as a vendor-firmware exposure management issue. The affected product range is broad, but urgency cannot be rated from the supplied sources because severity and impact details are missing. Focus on inventory, OEM confirmation, and firmware update tracking.

Technical view

The issue is described as a time-of-check/time-of-use window during processing of storage SCM commands, where a pointer may become invalid at a specific execution point. Affected scope spans Qualcomm Snapdragon Auto, Compute, Connectivity, Industrial IoT, Mobile, Wired Infrastructure, and Networking products.

Likely exposure

Exposure is most likely in devices, vehicles, embedded systems, mobile devices, or networking platforms using affected Qualcomm Snapdragon components. Actual risk depends on OEM firmware integration and whether the deployed hardware maps to Qualcomm’s affected component list.

Exploitation context

The provided bundle does not cite active exploitation, public exploitation, or inclusion in CISA KEV. No exploitability conditions, privileges, or attack path are provided, so exploitation status should be treated as unconfirmed.

Researcher notes

Source evidence is sparse: no CVSS, CWE, CPEs, exploit prerequisites, or impact statement are provided. Analysis should center on Qualcomm bulletin details and downstream OEM mapping rather than assuming a universal device-level impact.

Mitigation direction

  • Check Qualcomm’s March 2021 bulletin for vendor guidance.
  • Request OEM firmware status for affected device models.
  • Prioritize updates for internet-connected, fleet, or safety-relevant devices.
  • Track devices without available OEM fixes as exceptions.
  • Monitor Qualcomm and OEM advisories for revised guidance.

Validation and detection

  • Inventory deployed Qualcomm Snapdragon chipsets and firmware versions.
  • Map device models against Qualcomm’s affected product list.
  • Confirm whether OEM firmware includes the March 2021 Qualcomm security content.
  • Review procurement or SBOM records for listed Qualcomm components.
  • Document systems where component mapping cannot be confirmed.
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-11220 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 Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and NetworkingAQT1000, AR8035, PM4125, PM4250, PM6125, PM6150, PM6150A, PM6150L, PM6350, PM640A, PM640L, PM640P, PM7250B, PM8004, PM8005, PM8008, PM8350, PM855, PM855A, PM855B, PM855L, PM855P, PM8998, PMD9655, PMI632, PMI8998, PMK8002, PMK8003, PMM8195AU, PMM855AU, PMX24, PMX50, PMX55, QAT3519, QAT3522, QAT3550, QAT3555, QAT5515, QAT5516, QBT1500, QBT2000, QCA6390, QCA6420, QCA6430, QCA6574A, QCA6574AU, QCA6595, QCA6696, QCA9984, QCM2290, QCM4290, QCS2290, QCS405, QCS4290, QDM2301, QDM2302, QET4101, QET5100, QPA4360, QPA4361, QPA5460, QPA6560, QPA8673, QSW6310, QSW8573, QSW8574, QTC410S, QTC800H, QTC800S, QTC801S, QTM525, SA6155P, SA8155, SA8155P, SA8195P, SD 8C, SD 8CX, SD460, SD480, SD662, SD665, SD675, SD855, SD888 5G, SDM830, SDR051, SDR052, SDR425, SDR660, SDR660G, SDR735, SDR735G, SDR8150, SDR8250, SDR865, SDX24, SDX50M, SDX55, SDX55M, SM4125, SMB1351, SMB1354, SMB1355, SMB1381, SMB1390, SMB1396, SMR526, SMR545, SMR546, WCD9340, WCD9341, WCD9360, WCD9370, WCD9375, WCD9385, WCN3910, WCN3950, WCN3980, W ...[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.