CVE-2017-11076
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 · uneditedOn some hardware revisions where VP9 decoding is hardware-accelerated, the frame size is not programmed correctly into the decoder hardware which can lead to an invalid memory access by the decoder.
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 memory corruption vulnerability exists in hardware-accelerated VP9 video decoding on certain hardware revisions. The frame size is not correctly programmed into the decoder hardware, causing the decoder to perform invalid memory accesses during video processing, potentially leading to arbitrary 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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 Qualcomm chipset modelCheck the device system information, bootloader, or /proc/cpuinfo to determine the exact chipset (e.g., Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 425, Sd 427, Sd 430)Affected if The chipset matches one of the affected models: Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 425, Sd 427, or Sd 430
-
Verify VP9 hardware decoding is in useInspect active media pipelines, video player settings, or system logs to determine if VP9 decoding is being handled by hardware acceleration rather than software decodingAffected if VP9 content is being decoded using the hardware decoder (e.g., via V4L2, MediaCodec, or platform-specific video APIs with hardware acceleration enabled)
-
Check the firmware versionQuery the firmware or baseband firmware version through system utilities (e.g., atfwd, diagnostic logs, or /vendor/firmware)Affected if The device runs any firmware version on the affected chipsets, since all versions are listed as vulnerable
-
Confirm hardware VP9 decode capability is exposedEnumerate available video decode capabilities through media APIs (e.g., android.media.MediaCodecList, v4l2-ctl --list-devices, or GPUinfo) to see if a VP9 hardware decoder is exposed to applicationsAffected if A hardware VP9 decoder is available and accessible to applications on the system
A system is affected if it uses one of the listed Qualcomm chipsets (Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205, Sd 425, Sd 427, Sd 430) and has VP9 hardware-accelerated decoding enabled or in use.
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-provided firmware and/or driver updates for affected hardware revisions that correctly initialize frame size parameters in the VP9 hardware decoder. Until patched, avoid processing untrusted VP9 content on affected devices.
- 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-11076 — 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-11076 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