CVE-2017-11054
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 for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, while processing a specially crafted cfg80211 vendor command, a buffer over-read can occur.
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 confidenceA buffer over-read vulnerability exists in the Linux kernel's cfg80211 vendor command processing within Android releases from CAF. When handling a specially crafted cfg80211 vendor command, the kernel reads beyond the allocated buffer boundary, potentially exposing sensitive kernel memory or causing unpredictable behavior.
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 data= 8.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Android version is 8.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The version shows exactly 8.0 (Oreo)
-
Confirm cfg80211 kernel module is loadedRun 'lsmod | grep cfg80211' or check /proc/modules via ADB shellAffected if cfg80211 module is present and loaded
-
Check if Wi-Fi is enabled and vendor commands may be processedRun 'iw list' via ADB shell to enumerate cfg80211 supported vendor commands, or check Wi-Fi status in SettingsAffected if Wi-Fi is enabled and the system supports vendor-specific cfg80211 commands
-
Identify kernel version and buildRun 'uname -a' via ADB shell to check kernel version, noting if it is a CAF (Code Aurora Forum) or stock Google kernelAffected if Kernel is built from CAF sources for Android 8.0 without the security patch
A system is affected if it is running Android 8.0 with cfg80211 vendor command support enabled, and the kernel lacks the specific fix for this buffer over-read 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 vendor patch from CAF/Google for this vulnerability or update to an Android security patch level that includes the fix. Since this is a kernel-level cfg80211 issue, ensure thorough Wi-Fi functionality testing after patching.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11054 — 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-11054 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