dbcve.org
AndroidOperating system · Google

CVE-2017-11053

HIGH · 7.8 CVSS v3.0 Published 2017-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, when qos map set IE of length less than 16 is received in association response or in qos map configure action frame, a buffer overflow can potentially occur in ConvertQosMapsetFrame().

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 confidence

A buffer overflow vulnerability exists in the ConvertQosMapsetFrame() function within the Linux kernel's WiFi subsystem (used in Android for MSM, Firefox OS for MSM, and QRD Android). When a QoS map set Information Element with length less than 16 is received in an association response or QoS map configure action frame, the function fails to properly validate the input length before copying data into a fixed-size buffer, leading to overflow. This kernel-level flaw could allow local privilege escalation or denial of service.

MitigationApply the relevant security patch from the Code Aurora Forum (CAF) and Google Android security bulletins to the affected kernel/source code. For end-users, apply available system/firmware updates for affected Android devices.

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
AndroidOperating system
Affected:= 8.0

CVSS 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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Android version is 8.0
    Check the device settings under Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via adb shell
    Affected if The device is running Android 8.0 exactly (version code '8.0' or 'OPR6.170623.010' or similar 8.0 builds)
  2. Verify WiFi functionality is enabled
    Check if WiFi is turned on or if the device has WiFi capability. The vulnerable code path is in the kernel WiFi subsystem processing QoS map set frames during association.
    Affected if WiFi is enabled and the device processes association response or QoS map configure action frames
  3. Identify if the device uses a Qualcomm MSM chipset
    Check the device hardware info via 'getprop ro.hardware' or 'getprop ro.board.platform' in adb shell, or check kernel boot logs for MSM WiFi driver loading
    Affected if The device uses a Qualcomm MSM (Mobile Station Modem) chipset, which is the specific platform listed as affected
  4. Check kernel WiFi subsystem version
    Inspect the kernel version and config for cfg80211 or WiFi driver modules: 'uname -a' and check /proc/config.gz if available, or review the kernel source for the ConvertQosMapsetFrame function presence
    Affected if The kernel contains the vulnerable ConvertQosMapsetFrame function in the WiFi subsystem (cfg80211 or related driver)

A device is affected if it runs Android 8.0 on Qualcomm MSM hardware with WiFi enabled, and the kernel contains the unpatched ConvertQosMapsetFrame function that processes QoS map set Information Elements with insufficient length validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant security patch from the Code Aurora Forum (CAF) and Google Android security bulletins to the affected kernel/source code. For end-users, apply available system/firmware updates for affected Android devices.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-11053 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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