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

> A non-privileged user can exploit a use-after-free in the Arm Mali GPU driver to gain elevated privileges or execute code on Android devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Mar 2023
- **Updated:** 27 Nov 2024
- **Also known as:** A-267357916, ASB-A-267357916, GHSA-fpqq-p5q5-4fhw

## What is CVE-2022-46395?

CVE-2022-46395 is a high-severity use after free vulnerability in Arm Valhall Gpu Kernel Driver, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the Arm Mali GPU Kernel Driver. A non-privileged user can make improper GPU processing operations to gain access to already freed memory. This affects Midgard r0p0 through r32p0, Bifrost r0p0 through r41p0 before r42p0, Valhall r19p0 through r41p0 before r42p0, and Avalon r41p0 before r42p0.

Weakness: CWE-416 (Use After Free)

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

It affects 4 products.


Products: Arm Avalon Gpu Kernel Driver, Arm Bifrost Gpu Kernel Driver, Arm Midgard Gpu Kernel Driver, Arm Valhall Gpu Kernel Driver.

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

Apply the vendor's patch.

## Is CVE-2022-46395 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46395 exists.

Public exploit code:

- https://github.com/SmileTabLabo/CVE-2022-46395 (github_poc): https://github.com/SmileTabLabo/CVE-2022-46395
- CVE-2022-46395 POC for FireTV 3rd gen Cube (gazelle)  (github_poc): https://github.com/Pro-me3us/CVE_2022_46395_Gazelle
- CVE-2022-46395 POC for FireTV 2nd gen Cube (raven)  (github_poc): https://github.com/Pro-me3us/CVE_2022_46395_Raven
- https://github.com/Gao-Zuin/cve-2022-46395-qemu (github_poc): https://github.com/Gao-Zuin/cve-2022-46395-qemu

## Other vulnerabilities in Arm Valhall Gpu Kernel Driver

- [CVE-2022-46394](https://insights.sbomify.com/CVE-2022-46394/): Use after free in n/a (high 8.8)
- [CVE-2023-28469](https://insights.sbomify.com/CVE-2023-28469/): Use after free in n/a (medium 5.5)
- [CVE-2023-28147](https://insights.sbomify.com/CVE-2023-28147/): Use after free in n/a (medium 5.5)
- [CVE-2022-46396](https://insights.sbomify.com/CVE-2022-46396/): Memory corruption in n/a (medium 4.4)
- [CVE-2022-46781](https://insights.sbomify.com/CVE-2022-46781/): Memory corruption in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46395 is a high-severity use after free vulnerability in Arm Valhall Gpu Kernel Driver, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46395 exists.

Affected product: Arm Valhall Gpu Kernel Driver. 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-46395/ (Markdown: https://insights.sbomify.com/CVE-2022-46395/index.md)
```

## Sources

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

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