CVE-2014-9910
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: N/A. Android ID: A-31746399. References: B-RB#26710.
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 local privilege escalation vulnerability in the Broadcom Wi-Fi driver allows a malicious Android application to execute arbitrary code within kernel context. The attacker first compromises a privileged process, then exploits a flaw in the Wi-Fi driver to escalate to kernel-level code execution.
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<= 7.1.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
- 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 Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 7.1.0 or lower (Android Nougat 7.1.0 and earlier)
-
Confirm Broadcom Wi-Fi hardwareCheck device specifications for Broadcom Wi-Fi chip, or run 'getprop ro.board.platform' and inspect Wi-Fi driver modules via 'ls /system/lib/modules/wlan/'Affected if Device uses a Broadcom Wi-Fi chipset
-
Check applied security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than November 2016 (the month when the fix was released)
-
Identify kernel context exposureReview installed apps for suspicious privileges, or check if 'wlan' kernel module is loaded via 'lsmod | grep wlan'Affected if A compromised privileged app could leverage the Wi-Fi driver flaw to gain kernel-level code execution
The device is affected if it runs Android 7.1.0 or earlier, contains a Broadcom Wi-Fi chip, and lacks the November 2016 or later security patch that addresses this 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 Android security patches provided by the device OEM, which should include the updated Broadcom Wi-Fi driver. Users on affected devices should prioritize installing the latest system updates.
- Consultation8.0 h
- Implementation24.0 h
- Testing32.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $21,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9910 — 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-2014-9910 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