# CVE-2022-34830: Use after free in n/a

> A race condition in the Android GPU driver allows non-privileged users to access freed memory, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Nov 2022
- **Updated:** 28 Apr 2025
- **Also known as:** A-227655299, ASB-A-227655299, GHSA-3f72-rqqj-2fm8

## What is CVE-2022-34830?

CVE-2022-34830 is a high-severity use after free vulnerability in n/a, published on 23 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Arm product family through 2022-06-29 has a TOCTOU Race Condition that allows non-privileged user to make improper GPU processing operations to gain access to already freed memory.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Arm Utgard Gpu Kernel Driver.

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

Apply the vendor's patch.

## Is CVE-2022-34830 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34830 is a high-severity use after free vulnerability in n/a, published on 23 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34830 in the wild and no public exploit code.

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

## Sources

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

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