CVE-2017-11051
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, information disclosure is possible in function __wlan_hdd_cfg80211_testmode since buffer hb_params is not initialized to zero.
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 confidenceInformation disclosure vulnerability in the WLAN driver function __wlan_hdd_cfg80211_testmode where the hb_params buffer is not initialized to zero before use, causing uninitialized stack memory contents to potentially leak to userspace.
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.
-
Confirm Android version is 8.0Run 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version is exactly 8.0; versions other than 8.0 are not in the affected range
-
Identify WLAN driver in useCheck /proc/kallsyms or kernel modules for symbols containing '__wlan_hdd_cfg80211_testmode' or examine the WLAN driver module loaded on the deviceAffected if The device uses a WLAN driver containing the __wlan_hdd_cfg80211_testmode function from the affected codebase
-
Verify cfg80211 testmode interface is accessibleCheck if cfg80211 testmode is enabled and accessible via 'iw' utility or wpa_supplicant control interface; attempt to enumerate testmode capabilities if the interface existsAffected if cfg80211 testmode interface is enabled and the device supports testmode operations, allowing userspace to trigger the vulnerable code path
-
Inspect driver for uninitialized buffer usageAnalyze the __wlan_hdd_cfg80211_testmode function in the WLAN driver binary/module for the hb_params buffer usage without prior memset to zeroAffected if The driver's testmode function uses hb_params without zero-initialization, allowing stack memory disclosure to userspace
The device is affected only if it runs Android 8.0, uses the vulnerable WLAN driver containing __wlan_hdd_cfg80211_testmode, and has cfg80211 testmode functionality accessible to trigger the uninitialized buffer leak.
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 dataInitialize the hb_params buffer to zero before use in the affected function. Apply the vendor/CAF patch for this vulnerability and update to a patched Android kernel version.
- 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-11051 — 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-11051 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