CVE-2017-8267
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, a race condition exists in an IOCTL handler potentially leading to an integer overflow and then an out-of-bounds write.
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 confidenceRace condition in a kernel IOCTL handler in Qualcomm Android kernels from CAF allows an integer overflow to occur, potentially leading to an out-of-bounds memory write. This is a privilege escalation vulnerability in kernel space.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/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 kernel processor typeRun 'cat /proc/cpuinfo' or 'uname -a' and look for ' Qualcomm ' in the processor or hardware informationAffected if The device does not use a Qualcomm Snapdragon or other Qualcomm processor (the vulnerability is specific to Qualcomm kernels)
-
Confirm kernel architecture is ARM/ARM64Run 'uname -m' - this vulnerability affects ARM and ARM64 architectures in Qualcomm Android kernelsAffected if The kernel is not running on ARM or ARM64 architecture (the flaw exists in ARM-specific Qualcomm kernel code)
-
Check the kernel version stringRun 'cat /proc/version' or 'uname -r' to display the running kernel versionAffected if The kernel version is older than the patched version released in the May 2017 Android security bulletin (no specific version number provided)
-
Verify the security patch levelGo to Settings > About Phone > Build Number, or run 'getprop ro.build.version.security_patch' to check the Android security patch levelAffected if The device security patch level is earlier than May 2017 (the patch was released in the May 2017 Android security update)
-
Check for the vulnerable IOCTL handler presenceThis requires kernel source inspection - the flaw exists in a specific Qualcomm kernel IOCTL handler handling video memory allocation; check if the kernel is built from unpatched CAF (Code Aurora Forum) sourcesAffected if The kernel was built from unpatched Qualcomm CAF sources prior to the May 2017 security update
A user is affected if their Android device uses a Qualcomm processor and has a kernel version or security patch level predating the May 2017 Android security bulletin.
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 vendor-specific kernel patch from Qualcomm/Google in the next security update cycle; this is a kernel-level fix requiring vendor firmware update.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8267 — 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-8267 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