CVE-2017-0825
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 information disclosure vulnerability in the Broadcom wifi driver. Product: Android. Versions: Android kernel. Android ID: A-37305633. References: B-V2017063002.
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 · low confidenceAn information disclosure vulnerability exists in the Broadcom wifi driver within the Android kernel. The flaw allows unprivileged applications or actors to potentially access sensitive information through the driver's improper handling of memory or data access controls. This is a kernel-level component vulnerability affecting Android devices with Broadcom wifi chipsets.
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 Android version is 8.0 or lower (8.0, 7.x, 6.x, etc.)
-
Identify the wifi chipset vendorCheck device specifications for wifi hardware, or run 'getprop ro.wifi.interface' and inspect kernel modules via 'lsmod' in ADB shell to look for Broadcom driver modules (e.g., bcmdhd, wl, brcmfmac)Affected if Device uses a Broadcom wifi chipset (look for bcmdhd, wl, brcmfmac, or similar Broadcom kernel modules)
-
Verify the kernel driver versionRun 'modinfo <bcmdhd|wl|brcmfmac>' in ADB shell to retrieve driver version information, or check '/proc/modules' for loaded Broadcom wifi modulesAffected if Broadcom wifi driver is loaded and cannot be verified as patched (no available version string or version predates June 2017)
-
Confirm kernel-level accessCheck if the device has root access or run 'dmesg | grep -i broadcom' via ADB shell to observe driver initialization messagesAffected if Kernel logs show Broadcom driver initialization without evidence of post-June-2017 security patches applied
A device is affected if it runs Android 8.0 or earlier AND contains a Broadcom wifi chipset with the vulnerable driver, as the flaw requires both the affected Android version range and the specific hardware component to be present.
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 released after June 2017, which include the fix for this Broadcom driver vulnerability. Users should ensure their devices receive kernel and firmware updates from their device manufacturers.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0825 — 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-0825 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