LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11162: u'Possible buffer overflow in MHI driver due to lack of input parameter validation of EOT events received f...

u'Possible buffer overflow in MHI driver due to lack of input parameter validation of EOT events received from MHI device side' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in Agatti, APQ8009, Bitra, IPQ4019, IPQ5018, IPQ6018, IPQ8064, IPQ8074, Kamorta, MDM9607, MSM8917, MSM8953, Nicobar, QCA6390, QCM2150, QCS404, QCS405, QCS605, QM215, QRB5165, Rennell, SA415M, SA515M, SA6155P, SA8155P, Saipan, SC8180X, SDM429, SDM429W, SDM439, SDM450, SDM632, SDM710, SDM845, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130

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

Security readout for executives and security teams

Plain-English summary

This Qualcomm issue is a possible buffer overflow in a low-level Snapdragon MHI driver. A flaw in validating EOT events from the device side could let malformed device-side input corrupt memory. The sources list many Snapdragon platforms, but do not provide CVSS, business impact detail, or confirmed exploitation.

Executive priority

Handle this as a firmware supply-chain exposure review. The affected product range is broad, but the public evidence lacks severity scoring and active exploitation confirmation. Prioritize inventory, vendor confirmation, and patch availability over emergency response.

Technical view

CVE-2020-11162 concerns insufficient input parameter validation for EOT events received from the MHI device side in Qualcomm's MHI driver. The CVE affects broad Snapdragon Auto, Compute, Connectivity, IoT, Mobile, Wearables, Voice & Music, and Wired Infrastructure and Networking product families, including numerous named chipsets.

Likely exposure

Exposure is most likely in products using the named Qualcomm Snapdragon chipsets or platform families. This may include embedded, mobile, automotive, connectivity, and networking devices. The sources do not identify specific OEM devices, firmware versions, or operating systems.

Exploitation context

The CVE is not marked as CISA KEV in the provided bundle. The cited sources do not report active exploitation, public exploit availability, or attacker prerequisites. Treat exploitation status as unconfirmed.

Researcher notes

Key gaps are severity, exact affected firmware versions, exploitability conditions, and patch identifiers. Analysis should stay tied to Qualcomm and OEM advisories because the CVE description names chipset families, not finished commercial devices.

Mitigation direction

  • Review Qualcomm's October 2020 security bulletin and affected chipset list.
  • Request OEM firmware or driver guidance for devices using listed Snapdragon parts.
  • Prioritize supported assets with exposed connectivity, embedded, or fleet roles.
  • Apply vendor-provided security updates where available.
  • Plan replacement or isolation for unsupported affected devices.

Validation and detection

  • Inventory hardware for the listed Qualcomm Snapdragon chipsets and platform families.
  • Map affected chipsets to OEM model, firmware, and support status.
  • Confirm whether OEM updates reference Qualcomm's October 2020 bulletin or CVE-2020-11162.
  • Check vulnerability records for missing CVSS, CWE, or exploitation updates before risk scoring.
  • Document exceptions where firmware status cannot be verified.
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-11162 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and NetworkingAgatti, APQ8009, Bitra, IPQ4019, IPQ5018, IPQ6018, IPQ8064, IPQ8074, Kamorta, MDM9607, MSM8917, MSM8953, Nicobar, QCA6390, QCM2150, QCS404, QCS405, QCS605, QM215, QRB5165, Rennell, SA415M, SA515M, SA6155P, SA8155P, Saipan, SC8180X, SDM429, SDM429W, SDM439, SDM450, SDM632, SDM710, SDM845, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130Listed
Weakness

CWE details

No CWE listed

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