dbcve.org
AndroidOperating system · Google

CVE-2015-9028

HIGH · 7.8 CVSS v3.0 Published 2017-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
In all Android releases from CAF using the Linux kernel, a buffer overflow vulnerability exists in a cryptographic routine.

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 confidence

A buffer overflow vulnerability exists in a cryptographic routine within the Linux kernel used in Android releases from CAF (Code Aurora Forum). The flaw allows potential code execution or denial of service via the overflow in the crypto subsystem.

MitigationApply the CAF/Qualcomm kernel security patch for CVE-2015-9028 and deploy via Android OTA updates; coordinate with device OEMs for patch availability.

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 data
AndroidOperating system
Affected:all versions

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Any Android version is running (per the all-versions-affected designation)
  2. Identify kernel version
    Run 'uname -r' or 'cat /proc/version' via ADB shell
    Affected if Kernel version is from CAF/Qualcomm (the CVE originates from Code Aurora Forum) and the crypto subsystem is in use
  3. Check crypto subsystem modules
    Run 'ls -la /proc/crypto' or 'cat /proc/crypto' via ADB shell to list loaded cryptographic modules
    Affected if Crypto modules are actively loaded (the overflow occurs in the crypto routine)
  4. Verify kernel build fingerprint
    Run 'getprop ro.build.fingerprint' via ADB shell to identify if the build is CAF/Qualcomm-based
    Affected if The device uses a CAF/Qualcomm kernel build (the vulnerability exists in CAF kernel code)
  5. Check for available security updates
    Run 'getprop ro.build.version.security_patch' via ADB shell to check the last security patch date
    Affected if Security patch level is earlier than the CVE fix date (no specific patch applied)

If the device runs any Android version with an active CAF/Qualcomm kernel and loaded crypto subsystem without the CVE-2015-9028 patch applied, the environment is affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the CAF/Qualcomm kernel security patch for CVE-2015-9028 and deploy via Android OTA updates; coordinate with device OEMs for patch availability.

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,384.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-9028 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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