Linux KernelOperating system · Linux
CVE-2017-0571
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 Broadcom Wi-Fi driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process. Product: Android. Versions: Kernel-3.10, Kernel-3.18. Android ID: A-34203305. References: B-RB#111541.
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 in the Broadcom Wi-Fi driver allows a local malicious application to execute arbitrary code within kernel context. The issue requires first compromising a privileged process and affects Android devices running Kernel-3.10 and Kernel-3.18.
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
Linux KernelOperating system
= 3.10= 3.18CVSS 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.
-
Check the kernel versionRun 'uname -r' or check /proc/version to identify the running kernel versionAffected if The kernel version is exactly 3.10 or 3.18
-
Confirm this is an Android deviceCheck if the device runs Android OS (check /system/build.prop or verify mobile OS)Affected if The device is NOT an Android device (this is an Android-specific vulnerability)
-
Identify Wi-Fi hardware vendorCheck Wi-Fi adapter information via 'wmic' on Windows, 'lspci' or 'lsusb' on Linux, or check device specificationsAffected if The device does NOT have Broadcom Wi-Fi hardware
-
Check if Wi-Fi driver is loadedVerify the Wi-Fi interface exists and driver is active (check 'ip link' or 'ifconfig' for wlan0, or check kernel modules with 'lsmod')Affected if Wi-Fi is not enabled or the Broadcom Wi-Fi driver is not loaded
-
Check for security patch levelOn Android, check Settings > About Phone > Security patch level (or run 'getprop ro.build.version.security_patch')Affected if The Android security patch level is earlier than the patch that addresses CVE-2017-0571
A user is affected if the device is an Android device with Broadcom Wi-Fi hardware, running kernel 3.10 or 3.18, with the Wi-Fi driver enabled, and without the corresponding Android security patch applied.
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 Android security patches that address this Broadcom Wi-Fi driver vulnerability; contact device OEM for availability if not yet deployed.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.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 $5,792.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0571 — 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-0571 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