CVE-2015-9070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn all Qualcomm products with Android releases from CAF using the Linux kernel, a buffer over-read vulnerability exists in a TrustZone syscall.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA buffer over-read vulnerability exists in a TrustZone syscall within Qualcomm Android devices using Linux kernel releases from CAF (Code Aurora Forum). TrustZone provides ARM's Trusted Execution Environment (TEE) for secure processing, and this flaw could allow reading sensitive data from protected memory regions or potentially escaping the TEE sandbox.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device chipset manufacturerCheck the device hardware specifications or use commands like 'getprop ro.hardware' or 'cat /proc/cpuinfo' to determine if the device uses a Qualcomm Snapdragon chipsetAffected if The device does NOT use a Qualcomm chipset - the vulnerability is specific to Qualcomm processors
-
Verify the kernel source is from Code Aurora Forum (CAF)Check kernel version strings or build information using 'uname -a' or 'cat /proc/version' to see if the kernel includes CAF branchesAffected if The kernel is NOT built from CAF sources - the flaw exists specifically in CAF kernel releases for Qualcomm processors
-
Confirm TrustZone/TEE is present on the deviceCheck for Trusted Execution Environment by looking for /dev/tz_* device nodes, or using 'getprop' to check for 'ro.trustonic' or 'ro.trusty' properties, or checking /sys/class/misc/tz*/ for TrustZone entriesAffected if TrustZone is NOT present or not initialized - the vulnerability only applies when TrustZone is active as the secure OS
-
Check if the device runs a mainline Android versionUse 'getprop ro.build.version.sdk' to determine the Android SDK version, as this vulnerability affects all Android versions on affected hardwareAffected if The device is NOT running Android (e.g., is a non-Android embedded system) - though the primary target is Android devices
The device is affected if it uses a Qualcomm chipset with a CAF-derived kernel and has TrustZone/TEE enabled, regardless of Android version, as this is a firmware-level flaw in the TrustZone syscall implementation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Qualcomm/CAF firmware and Android security patch updates addressing this TrustZone vulnerability. Users should ensure devices receive the latest security updates from their device manufacturers.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-9070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data