Security readout for executives and security teams
CVE-2016-10385 is a Qualcomm Android issue involving memory being used after it should have been freed. The public record ties it to IMS RCS on Android releases from CAF using the Linux kernel. Business urgency depends on whether affected Snapdragon-based Android devices remain in service and whether OEM security updates were applied. Exposure is most plausible for older Android devices built on the listed Qualcomm Snapdragon platforms, especially OEM firmware derived from CAF Android kernel releases. Current exposure cannot be inferred from chipset alone; it depends on device model, firmware lineage, Android security patch level, and whether vendor fixes were shipped and installed. Medium tracking priority unless affected legacy Android fleets remain active. Escalate if critical business devices use the listed Qualcomm platforms without confirmed OEM security updates. The record lacks enough severity and exploitation evidence for a higher source-grounded priority. Mitigation focus: Review Android and OEM advisories for CVE-2016-10385 applicability.; Inventory Android devices using the listed Snapdragon platforms.; Deploy applicable OEM firmware or Android security updates after testing..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2016-10385 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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/2017-07-01CVE reference · x_refsource_CONFIRM
- https://source.android.com/security/bulletin/2018-04-01CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.