CVE-2017-6423
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 · uneditedAn elevation of privilege vulnerability in the Qualcomm kyro L2 driver. Product: Android. Versions: Android kernel. Android ID: A-32831370. References: QC-CR#1103158.
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 Qualcomm kyro L2 driver within the Android kernel. The vulnerability allows a locally installed malicious application to potentially escalate privileges due to improper input validation or access control in the L2 cache driver, which operates at a privileged kernel 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:L/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 is running AndroidCheck the device's OS settings or run 'getprop ro.build.version.release' in ADB shell to verify the operating system is AndroidAffected if The device is running any version of Android (as all versions are affected according to the provided data)
-
Identify if the device uses Qualcomm hardware with kyro L2 driverCheck the kernel config or module list for 'kyro' or 'qcom' L2 cache driver references. On a rooted device or through ADB, inspect /proc/config.gz or examine loaded kernel modules with 'lsmod'Affected if The device contains a Qualcomm processor with the kyro L2 cache driver present in the kernel (the vulnerability exists in this specific driver)
-
Verify if the L2 cache driver is accessible to user applicationsCheck the kernel module permissions and SELinux context for the kyro L2 driver module. Examine /sys/module/kyro_l2* permissions or review SELinux policies related to the driverAffected if The kyro L2 driver is accessible without proper kernel-level restrictions, allowing a locally installed application to interact with it
-
Check for available security patchesReview the Android Security Bulletin for the month containing CVE-2017-6423 and verify if your device manufacturer has released the corresponding security patch level. Check 'getprop ro.build.version.security_patch' in ADBAffected if The device security patch level is earlier than the patch that addresses this CVE (typically the Android security bulletin for September 2017 or later)
A user is affected if their Android device contains a Qualcomm processor with the kyro L2 cache driver and has not received the vendor security patch addressing this vulnerability.
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 Android security patch for the relevant Android version (as documented in the Android Security Bulletin). This is a kernel-level fix that requires updating the device with the vendor-supplied security patch containing the corrected Qualcomm kyro L2 driver.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6423 — 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-6423 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