CVE-2015-9035
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 memory buffer fails to be freed after it is no longer needed potentially resulting in memory exhaustion.
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 memory buffer in Qualcomm Android/Linux kernel products is not properly freed after use, creating a memory leak that can lead to memory exhaustion. This is a use-after-free/memory management vulnerability in CAF (CodeAurora Forum) kernel code.
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.
-
Confirm the system is running AndroidRun 'uname -a' or check /proc/version to verify the operating system is Android-basedAffected if The system is not running Android - this vulnerability only affects Android devices with Qualcomm kernel code
-
Identify the kernel versionRun 'uname -r' or check /proc/version to obtain the exact kernel version stringAffected if The kernel version matches an Android release that contains the vulnerable CAF memory management code
-
Verify the kernel is Qualcomm CAF-basedExamine the kernel version string or /proc/version for Qualcomm or CAF (CodeAurora Forum) identifiers in the build informationAffected if The kernel is built from Qualcomm CAF sources - the vulnerability exists specifically in CAF kernel code
-
Check for the vulnerable memory management code pathReview kernel source or symbols if accessible - the flaw is in improper deallocation of a memory buffer in CAF kernel codeAffected if The kernel contains the specific CAF memory management code that does not properly free buffers after use
-
Assess kernel patch levelCheck /proc/version for security patch date or examine if vendor security updates have been appliedAffected if The kernel lacks the Qualcomm/Google security fix that addresses this memory leak
A system is affected if it runs Android with a Qualcomm CAF kernel that contains the vulnerable memory buffer deallocation code and has not received the vendor security patch.
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 vendor-supplied security patches from Qualcomm/Google for Android releases; this requires a kernel-level fix to properly deallocate the memory buffer.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9035 — 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-9035 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