CVE-2014-10039: Qualcomm, Inc. Snapdragon Mobile vulnerability |…

CVE-2014-10039: In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9625, SD 400,...

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9625, SD 400, and SD 800, calling qsee_app_entry_return() without first calling qsee_app_entry() will cause the stack to be restored to an older state resulting in a return to an unexpected location.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 17, 2024, 00:30 UTC (UTC+00:00)

Security readout for executives and security teams

This is an older Android/Qualcomm vulnerability affecting devices using Snapdragon Mobile MDM9625, SD 400, and SD 800 chipsets with Android security patch levels before 2018-04-05. The flaw can cause execution to return to an unexpected location. Business risk is mainly from unmanaged or legacy Android devices that missed vendor security updates. Exposure is most likely on older Android phones, tablets, or embedded devices using the listed Qualcomm Snapdragon chipsets and running patch levels before 2018-04-05. Modern fully patched devices are less likely to be affected, but asset confirmation is required because OEM firmware support varies. Treat this as a legacy-device hygiene issue unless affected devices are still in production. Prioritize discovery of old Android assets, especially unmanaged mobile or embedded systems. Urgency rises if vulnerable devices handle sensitive data, connect to corporate networks, or cannot be patched. Mitigation focus: Identify Android devices using Qualcomm MDM9625, SD 400, or SD 800 chipsets.; Update affected devices to Android security patch level 2018-04-05 or later where available.; Check OEM and Qualcomm guidance for device-specific firmware availability..

Prepared: Jun 7, 2026, 14:11 UTC (UTC+00:00)

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-2014-10039 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: Apr 18, 2018, 14:00 UTC (UTC+00:00)

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

CVE List V5 sourceCVE List V5
https://source.android.com/security/bulletin/2018-04-01CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

Qualcomm, Inc.Snapdragon MobileMDM9625, SD 400, SD 800Listed

Weakness

CWE details

No CWE listed

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