LiveActive security incident?Get immediate response
CVE Record

CVE-2015-9199: In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdrag...

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile IPQ4019, MDM9625, MDM9635M, MDM9640, MDM9650, MDM9655, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, SD 808, SD 810, SD 820, and SD 820A, A non-secure region check is done while registering QSEE buffer address which is passed by HLOS but not while logging in the QSEE buffer, so corruption of dynamically protected secure region can occur if the non-secure buffer is changed between the time it's checked and when it's used.

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

Security readout for executives and security teams

This issue affects older Android devices using specific Qualcomm Snapdragon chipsets. A security check around a trusted execution buffer could be undermined if the buffer changed after checking, potentially corrupting protected secure memory. The bundle does not provide a CVSS score or active exploitation evidence. Exposure is limited to Android devices before the 2018-04-05 security patch level using listed Qualcomm Snapdragon Automobile or Mobile chipsets, including IPQ4019, several MDM modem families, and Snapdragon 205/210/212/400/410/412/415/615/616/800/808/810/820/820A. Treat this as a legacy Android device exposure issue. The business priority is finding affected Qualcomm-based devices and ensuring they are patched or retired. Urgency is higher for unsupported, embedded, automotive, or network-facing assets, but the bundle does not prove active exploitation. Mitigation focus: Update affected Android devices to the 2018-04-05 security patch level or later where available.; Check OEM and Qualcomm guidance for model-specific firmware availability.; Identify and retire unsupported affected devices that cannot receive security updates..

Prepared

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-2015-9199 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 Automobile, Snapdragon MobileIPQ4019, MDM9625, MDM9635M, MDM9640, MDM9650, MDM9655, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, SD 808, SD 810, SD 820, SD 820AListed
Weakness

CWE details

No CWE listed

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