# CVE-2020-11282: Missing authorization in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> Improper access control in the kgsl driver allows mapping GPU memstore to user space, potentially exposing sensitive data.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** 2748408, A-161374239, ASB-A-161374239, GHSA-mwrv-7784-j7w2

## What is CVE-2020-11282?

CVE-2020-11282 is a high-severity missing authorization vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, published on 22 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control when using mmap with the kgsl driver with a special offset value that can be provided to map the memstore of the GPU to user space in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

## Which versions are affected by CVE-2020-11282?

It affects 425 products.


Products: Qualcomm Apq8009, Qualcomm Apq8009w, Qualcomm Apq8017, Qualcomm Apq8037, Qualcomm Apq8053, Qualcomm Apq8064au, Qualcomm Apq8076, Qualcomm Apq8096au, Qualcomm Aqt1000, Qualcomm Ar6003, Qualcomm Ar8031, Qualcomm Ar8035, Qualcomm Ar8151, Qualcomm Csra6620, Qualcomm Csra6640, Qualcomm Csrb31024, Qualcomm Fsm10055, Qualcomm Fsm10056, Qualcomm Mdm8215, Qualcomm Mdm9206 and 405 more.

## How do I fix CVE-2020-11282?

Apply the vendor's patch.

## Is CVE-2020-11282 being exploited?

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

## Other vulnerabilities in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

- [CVE-2020-11283](https://insights.sbomify.com/CVE-2020-11283/): 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-2020-11136](https://insights.sbomify.com/CVE-2020-11136/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11137](https://insights.sbomify.com/CVE-2020-11137/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11138](https://insights.sbomify.com/CVE-2020-11138/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11143](https://insights.sbomify.com/CVE-2020-11143/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11282 and fix it if it is affected.

What it is: CVE-2020-11282 is a high-severity missing authorization vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, published on 22 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11282 in the wild and no public exploit code.

Affected product: Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables. 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-2020-11282/ (Markdown: https://insights.sbomify.com/CVE-2020-11282/index.md)
```

## Sources

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

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