# CVE-2017-11076: Use of Out-of-range Pointer Offset in Video

> Invalid memory access in hardware-accelerated VP9 decoding on specific Qualcomm Snapdragon revisions allows attackers to execute code or cause denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-3chv-hrqx-p726

## What is CVE-2017-11076?

CVE-2017-11076 is a high-severity memory corruption vulnerability in Qualcomm Msm8909w Firmware, published on 26 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On 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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-823 (Use of Out-of-range Pointer Offset)

## Which versions are affected by CVE-2017-11076?

It affects 27 products.


Products: Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 810 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware, Qualcomm Sd 835 Firmware, Qualcomm Sd 845 Firmware, Qualcomm Sdm429 Firmware and 7 more.

## How do I fix CVE-2017-11076?

No fix has been published for CVE-2017-11076 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-11076 being exploited?

There is no known exploitation of CVE-2017-11076 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Msm8909w Firmware

- [CVE-2019-2285](https://insights.sbomify.com/CVE-2019-2285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10509](https://insights.sbomify.com/CVE-2019-10509/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10538](https://insights.sbomify.com/CVE-2019-10538/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2255](https://insights.sbomify.com/CVE-2019-2255/): Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2259](https://insights.sbomify.com/CVE-2019-2259/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11076 and fix it if it is affected.

What it is: CVE-2017-11076 is a high-severity memory corruption vulnerability in Qualcomm Msm8909w Firmware, published on 26 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11076 in the wild and no public exploit code.

Affected product: Qualcomm Msm8909w Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11076/ (Markdown: https://insights.sbomify.com/CVE-2017-11076/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11076
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11076
- OSV: https://osv.dev/vulnerability/CVE-2017-11076

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11076/
Summaries are generated and may contain mistakes; the official description above is the record.