CVE-2017-15822
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 Qualcomm Android for MSM, Firefox OS for MSM, and QRD Android with all Android releases from CAF using the Linux kernel before security patch level 2018-04-05, while processing a 802.11 management frame, a buffer overflow may potentially 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 · moderate confidenceA buffer overflow vulnerability exists in the Linux kernel's 802.11 management frame processing code within Qualcomm-based Android platforms (MSM, Firefox OS for MSM, QRD Android). The flaw allows potential remote code execution or denial of service when processing specially crafted 802.11 management frames.
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 dataall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/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.
-
Identify the Android system and chipsetRun 'getprop ro.product.model' and 'getprop ro.board.platform' to confirm the device model and chipset platform. Check if the chipset is Qualcomm MSM-based.Affected if The device runs Android on a Qualcomm MSM (Mobile Station Modem) chipset platform.
-
Check the kernel versionRun 'uname -r' or 'cat /proc/version' to obtain the kernel version string.Affected if The kernel version predates the 2018-04-05 Android security patch and lacks the wireless driver fix for CVE-2017-15822.
-
Verify the wireless driver is loadedRun 'lsmod' or check '/proc/modules' for loaded wireless kernel modules related to 802.11 (such as cfg80211, wl12xx, or vendor-specific 802.11 drivers).Affected if A Qualcomm 802.11 wireless driver module is loaded and active, exposing the management frame processing code path.
-
Confirm management frame processing is activeRun 'iw list' or check wireless interface status via 'ip link show' and 'wpa_cli status' to verify the device is capable of processing 802.11 management frames.Affected if The wireless interface is up and the system processes 802.11 management frames, enabling the vulnerable code path.
A defender is affected if running Android on a Qualcomm MSM chipset with a kernel older than the 2018-04-05 patch level and with an active 802.11 wireless driver that processes management frames.
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 Android security patch level 2018-04-05 or later, which includes the kernel-level fix for this vulnerability. For non-Android Linux systems, update to a kernel version containing the patched wireless driver code.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15822 — 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-15822 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