CVE-2015-6634
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 · uneditedThe display drivers in Android before 5.1.1 LMY48Z allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bug 24163261.
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 confidenceThis is a memory corruption vulnerability in Android's display drivers (part of the media framework) that allows remote code execution or denial of service via a specially crafted media file. The vulnerability affects Android versions prior to 5.1.1 LMY48Z and stems from insufficient bounds checking or validation when processing media data in the display driver subsystem.
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<= 5.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
-
Check Android OS versionNavigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version displays 5.1 or lower (5.1, 5.0, 4.4.x, etc.)
-
Verify security patch levelNavigate to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Patch level shows a date before August 2015 or the field is empty or missing
-
Confirm build fingerprintRun 'getprop ro.build.fingerprint' via ADB to identify the exact build (e.g., LMY48Z indicates the patched version)Affected if Build does not contain 'LMY48Z' or a later build tag for Android 5.1.1
Device is affected if running Android version 5.1 or lower with a security patch level prior to August 2015 (or build earlier than LMY48Z).
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.
dbcve · scopedApply Android security patch level 2015-08-01 or later (included in Android 5.1.1 LMY48Z). For managed devices, enforce OS updates via MDM and consider network-level filtering of untrusted media content.
Android 5.1.1 LMY48Z or later
- Check the current Android version on the device (Settings > About Phone > Android version)
- Connect the device to a stable Wi-Fi network and ensure sufficient battery charge
- Check for system updates (Settings > About Phone > Check for updates) or check with device carrier/manufacturer for OTA updates
- Download and install Android 5.1.1 LMY48Z or later via OTA update or flash the factory image if OTA is unavailable
- After update, verify the device is running Android 5.1.1 LMY48Z or higher to confirm remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6634 — 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-6634 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