LiveActive security incident?Get immediate response
CVE Record

CVE-2017-18302: In Snapdragon (Automobile ,Mobile) in version MSM8996AU, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD...

In Snapdragon (Automobile ,Mobile) in version MSM8996AU, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016, a crafted HLOS client can modify the structure in memory passed to a QSEE application between the time of check and the time of use, resulting in arbitrary writes to TZ kernel memory regions.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw affects listed Qualcomm Snapdragon automotive and mobile platforms. A malicious high-level OS client could abuse a check/use timing gap to alter memory shared with a QSEE trusted application, potentially causing arbitrary writes into TrustZone kernel memory. That makes compromised or unpatched devices materially higher risk. Exposure is limited to devices using the listed Qualcomm Snapdragon Automobile or Mobile platforms and firmware containing the vulnerable Qualcomm closed-source component. Asset owners must map device models to chipsets and OEM firmware levels because the CVE sources do not identify every affected end product. Treat this as high priority where affected Snapdragon devices are still in service, especially automotive, enterprise mobile, or embedded fleets. The issue targets trusted execution memory, but public evidence in the bundle does not show active exploitation. Mitigation focus: Check Qualcomm, Android, and OEM advisories for CVE-2017-18302 guidance.; Apply OEM firmware updates that incorporate the relevant Qualcomm closed-source component fixes.; Prioritize affected automotive, managed mobile, and long-lived embedded devices..

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-2017-18302 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
3Source 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 Automobile, Snapdragon MobileMSM8996AU, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016Listed
Weakness

CWE details

No CWE listed

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