# CVE-2022-22075: Information Exposure in Graphics

> An attacker can read sensitive information during GPU context switches in Qualcomm Snapdragon devices, potentially exposing data to unauthorized users.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2023
- **Updated:** 3 Aug 2024
- **Also known as:** 3112398, 3129138, A-193434313, ASB-A-193434313, GHSA-wjfr-whqg-q776

## What is CVE-2022-22075?

CVE-2022-22075 is a medium-severity vulnerability in Qualcomm Apq8009 Firmware, published on 7 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Information Disclosure in Graphics during GPU context switch.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-22075?

It affects 183 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8009w Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8056 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Apq8076 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9628 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8108 Firmware, Qualcomm Msm8208 Firmware and 163 more.

## How do I fix CVE-2022-22075?

Apply the vendor's patch.

## Is CVE-2022-22075 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22075 and fix it if it is affected.

What it is: CVE-2022-22075 is a medium-severity vulnerability in Qualcomm Apq8009 Firmware, published on 7 Mar 2023. 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-2022-22075 in the wild and no public exploit code.

Affected product: Qualcomm Apq8009 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-2022-22075/ (Markdown: https://insights.sbomify.com/CVE-2022-22075/index.md)
```

## Sources

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

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