CVE-2017-13306
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 · uneditedA elevation of privilege vulnerability in the Upstream kernel mnh driver. Product: Android. Versions: Android kernel. Android ID: A-70295063.
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 elevation of privilege vulnerability exists in the Upstream kernel mnh driver for Android. The mnh driver appears to be a kernel-level component where improper access controls or input validation likely allows an attacker to escalate privileges from a lower-privileged context to root or kernel-level access.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Verify if mnh driver is present in the kernelCheck /proc/modules or run 'lsmod | grep mnh' to see if the mnh kernel module is loaded. Also check /sys/module/ for mnh presence.Affected if The mnh module is loaded or present on the device.
-
Check the kernel versionRun 'uname -r' or check /proc/version to obtain the running kernel version string.Affected if The kernel version predates the patch release date for CVE-2017-13306 (typically late 2017 or early 2018 kernels).
-
Check Android security patch levelRun 'getprop ro.build.version.security_patch' or check Settings > About Phone > Android security patch level.Affected if The security patch level is earlier than the February 2018 Android security update (which contained this fix).
-
Identify mnh driver file presenceCheck for the presence of mnh-related kernel objects: 'find /system/lib/modules -name '*mnh*' 2>/dev/null' or search kernel config for CONFIG_INTEL_MNH driver support.Affected if The mnh driver binary/module exists in the system and the kernel lacks the CVE-2017-13306 fix.
A device is affected if it has the mnh driver loaded, runs an unpatched kernel version (pre-February 2018 patch level), and lacks the CVE-2017-13306 upstream kernel fix.
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 the upstream kernel patch for CVE-2017-13306. For Android devices, this typically requires obtaining a patched kernel from the device manufacturer or through monthly security patch updates.
- Consultation4.0 h
- Implementation8.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,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13306 — 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-2017-13306 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