CVE-2017-17765
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 all Qualcomm products with Android releases from CAF using the Linux kernel, multiple values received from firmware are not properly validated in wma_get_ll_stats_ext_buf() and are used to allocate the sizes of buffers and may be vulnerable to integer overflow leading to buffer overflow.
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 confidenceInteger overflow vulnerability in wma_get_ll_stats_ext_buf() function within Qualcomm Wi-Fi driver (Linux kernel). Unvalidated values received from firmware are used directly to calculate buffer allocation sizes, allowing attackers to trigger buffer overflows via malicious firmware responses.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Verify device uses Qualcomm Wi-Fi hardwareCheck /proc/net/arp or Wi-Fi driver info in /sys/class/net/wlan0/device/ for Qualcomm identifiers; or run 'getprop | grep wifi' to check Wi-Fi chipset informationAffected if Device contains a Qualcomm Atheros Wi-Fi chip (typically identified by 'qca', 'atheros', or 'qualcomm' in driver/hardware info)
-
Confirm wma_get_ll_stats_ext_buf function is present in kernelSearch kernel symbols: 'grep wma_get_ll_stats_ext_buf /proc/kallsyms' (requires root) or check if Wi-Fi driver module loads the wlan module containing this functionAffected if The vulnerable function exists in the loaded Wi-Fi driver (function presence is required for the vulnerability to be exploitable)
-
Check if Wi-Fi is enabled and LL_stats extension feature is activeMonitor Wi-Fi operation status; the vulnerable code path executes when Wi-Fi is active and processing link layer statistics requests from firmwareAffected if Wi-Fi interface is up and actively communicating with firmware (vulnerability requires firmware interaction to trigger)
-
Review firmware version from vendorCheck Android build or Wi-Fi firmware version via 'getprop' or /vendor/firmware/ directory; compare to any available patched firmware versions from the device manufacturerAffected if Firmware version is unpatched and device accepts unvalidated size values from firmware responses
A defender is affected if their Android device uses Qualcomm Wi-Fi hardware with an unpatched driver that contains the wma_get_ll_stats_ext_buf function and has Wi-Fi enabled, allowing malicious firmware responses to trigger the integer overflow during buffer allocation calculations.
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 vendor-supplied Qualcomm firmware/driver patch; validate all firmware-provided values before use in size calculations; implement bounds checking on buffer allocation parameters.
- Consultation3.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,584.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17765 — 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-17765 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