CVE-2016-10346
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, an integer overflow vulnerability exists in the hypervisor.
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 confidenceAn integer overflow vulnerability exists in the hypervisor component of Qualcomm products running Android with Linux kernel from Code Aurora Forum (CAF). This flaw could allow an attacker to corrupt memory or potentially escape virtual machine isolation, leading to arbitrary code execution at the hypervisor level.
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 device uses a Qualcomm Snapdragon SoCCheck the device's processor information via 'cat /proc/cpuinfo' or through Settings > About Phone > Processor. Look for Qualcomm or Snapdragon branding.Affected if The device does not use a Qualcomm processor, as this vulnerability exists specifically in Qualcomm's hypervisor component.
-
Identify the baseband/MCP versionDial *#*#4636#*#* or check Settings > About Phone > Baseband version to retrieve the firmware version string.Affected if The device runs any baseband version on a Qualcomm platform, as the hypervisor flaw exists across versions and the CVE lists all Android versions as affected.
-
Verify the hypervisor module is presentCheck for hypervisor-related kernel modules or files in /sys/hypervisor/ or /dev/ (if accessible). Use 'ls -la /sys/firmware/' or search for 'hyp' in /proc/kallsyms if root access is available.Affected if The hypervisor module is loaded and active, as the integer overflow requires the hypervisor component to be running.
-
Check the Linux kernel source branchDetermine the kernel source by examining /proc/version or using 'uname -a'. Look for references to Code Aurora Forum (CAF) or qualcomm in the version string.Affected if The kernel is built from CAF sources, as the vulnerability specifically exists in the CAF-maintained hypervisor code.
A user is affected if their Android device uses a Qualcomm SoC with an active hypervisor built from Code Aurora Forum sources, since the CVE states all Android versions with this specific Qualcomm hypervisor component are vulnerable to the integer overflow.
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 firmware/hypervisor updates from Qualcomm; this is a platform-level vulnerability requiring OEM/carrier patch deployment rather than application-level fixes.
- 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-2016-10346 — 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-2016-10346 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