CVE-2017-11055
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 QCA_NL80211_VENDOR_SUBCMD_SET_WIFI_CONFIGURATION 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 handler used in Android CAF releases. When processing a specially crafted QCA_NL80211_VENDOR_SUBCMD_SET_WIFI_CONFIGURATION vendor command, the kernel reads beyond allocated buffer boundaries, potentially exposing sensitive memory contents or causing a denial of service.
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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version is exactly 8.0 (Oreo)
-
Verify cfg80211 module is loadedRun 'lsmod | grep cfg80211' or check /proc/modules via ADB shell to confirm the cfg80211 kernel module is presentAffected if The cfg80211 module is loaded and active on the device
-
Check for vendor command handler supportVerify the device uses Qualcomm WiFi drivers (common in Android CAF builds) by checking 'getprop ro.board.platform' or inspecting kernel config for CONFIG_CFG80211 and CONFIG_NL80211Affected if The device runs a CAF (Code Aurora Forum) kernel build with cfg80211 vendor extensions enabled
-
Confirm QCA vendor subcommand support existsCheck if the kernel binary contains the vulnerable QCA_NL80211_VENDOR_SUBCMD_SET_WIFI_CONFIGURATION handler by examining /proc/kallsyms or using 'strings' on the kernel image if accessibleAffected if The vendor-specific set_wifi_configuration subcommand handler is present in the running kernel
A device is affected if it runs Android 8.0 with a cfg80211-based Qualcomm WiFi driver that supports the QCA_NL80211_VENDOR_SUBCMD_SET_WIFI_CONFIGURATION vendor command.
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 patch from Qualcomm/CAF for the kernel's cfg80211 vendor command handling. Users should avoid using WiFi configuration utilities from untrusted sources until the system update containing the fix is installed.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.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,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11055 — 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-11055 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