CVE-2017-11050
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 Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, when the pktlogconf tool gives a pktlog buffer of size less than the minimal possible source data size in the host driver, a buffer overflow can 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 pktlogconf tool within Android CAF Linux kernel builds for MSM (Mobile Station Modem) platforms. When the pktlog buffer size is configured smaller than the minimal required source data size handled by the host driver, the tool can write beyond allocated buffer boundaries, leading to potential memory corruption.
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
- 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.
-
Confirm Android version is 8.0Check system property 'ro.build.version.release' via 'getprop ro.build.version.release' or settings menu About PhoneAffected if Version is not 8.0, the specific vulnerability in this CVE does not apply
-
Verify pktlogconf binary existsLocate the pktlogconf tool on the system using 'find / -name pktlogconf 2>/dev/null' or check common paths like /system/bin/, /vendor/bin/Affected if The tool is not present on the device, the vulnerability cannot be triggered
-
Check if pktlog kernel driver is loadedExamine loaded kernel modules via 'lsmod' or check /proc/modules for pktlog module, or check /sys/kernel/debug/pktlog if availableAffected if Pktlog driver is not loaded or available, the vulnerable code path is not exercised
-
Inspect pktlog buffer configurationCheck pktlog configuration files or runtime settings - look for buffer size parameters in /sys/module/pktlog/parameters/ or use 'pktlogconf -s' to query current settingsAffected if Buffer size is configured smaller than the minimal required source data size handled by the host driver, triggering the overflow condition
-
Review pktlog trace output for corruption indicatorsExamine pktlog output logs or trace buffers for signs of memory corruption, buffer overruns, or unexpected data patternsAffected if Unexpected memory patterns appear in pktlog output, indicating potential buffer overflow has occurred
The environment is affected only if running Android 8.0 with the pktlogconf tool present, pktlog driver loaded, and an undersized buffer configuration that triggers the boundary overflow condition.
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 vendor patch to enforce proper buffer size validation in pktlogconf, ensuring the buffer meets minimum size requirements before any data operations; verify the pktlog driver rejects undersized buffer allocations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11050 — 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-11050 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