CVE-2014-10051
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 Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, and SDX20, after loading a dynamically loaded code section, I-Cache is not invalidated, which could lead to executing code from stale cache lines.
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 · high confidenceThis is a CPU cache coherency vulnerability in Qualcomm Snapdragon processors where the instruction cache (I-Cache) is not invalidated after loading dynamically loaded code sections. This can cause the processor to execute stale instructions from cached memory lines instead of the newly loaded code, potentially allowing arbitrary code execution.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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 Qualcomm Snapdragon chip modelCheck the device specifications or system information to determine the exact chipset. Common methods: look at /proc/cpuinfo on Android, check device specs from manufacturer, or use a system information app.Affected if The device uses one of the affected models: Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, or Msm8909w
-
Confirm firmware version is presentAccess the firmware or baseband version information on the device. On Android, this is typically found in Settings > About Phone > Baseband version, or via AT commands for modem firmware.Affected if The firmware version is readable and matches one of the affected product lines (all versions of the listed models are affected)
-
Check if dynamic code loading is in useReview the application and system behavior to determine if the device loads code dynamically at runtime. This includes examining if apps use dlopen, dexclassloader, or similar mechanisms, or if the system uses dynamic library loading.Affected if The device or applications perform dynamic code loading - this is the condition that triggers the vulnerable code path
-
Verify Android security patch levelCheck the Android security patch level by going to Settings > About Phone > Android security patch level, or by running 'getprop ro.build.version.security_patch' via adb shell.Affected if The security patch level is earlier than 2018-04-05 (patches from this date contain the fix)
A device is affected if it uses one of the listed Qualcomm Snapdragon chip models, runs any firmware version of those models, performs dynamic code loading, and has not received the 2018-04-05 or later Android 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.
dbcve · scopedApply the Android security patch level from 2018-04-05 or later to affected devices. This is a firmware-level fix that must be provided by device manufacturers through OS updates.
Android security patch level 2018-04-05 or later (contact device manufacturer for specific firmware version)
- Check current Android security patch level on the device (Settings > About Phone > Security patch level)
- If the security patch level is earlier than April 5, 2018, initiate a system update
- Apply the latest available Android security update from your device manufacturer or carrier
- Verify after update that the security patch level shows April 5, 2018 or later
- Reboot the device to ensure all cache invalidation takes effect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.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,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-10051 — 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-2014-10051 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