# CVE-2023-6241: Mali GPU Kernel Driver allows improper GPU memory processing operations

> A local attacker can exploit a race condition in Mali GPU drivers to trigger a use-after-free, potentially leading to privilege escalation or code execution.

- **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:** 4 Mar 2024
- **Updated:** 13 Mar 2025
- **Also known as:** A-316206835, ASB-A-316206835, GHSA-p6cr-4f2h-m98v

## What is CVE-2023-6241?

CVE-2023-6241 is a high-severity use after free vulnerability in Arm Valhall Gpu Kernel Driver, published on 4 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use After Free vulnerability in Arm Ltd Midgard GPU Kernel Driver, Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user to exploit a software race condition to perform improper memory processing operations. If the system’s memory is carefully prepared by the user, then this in turn cause a use-after-free.This issue affects Midgard GPU Kernel Driver: from r13p0 through r32p0; Bifrost GPU Kernel Driver: from r11p0 through r25p0; Valhall GPU Kernel Driver: from r19p0 through r25p0, from r29p0 through r46p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r46p0.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2023-6241?

It affects 4 products.


Products: Arm 5th Gen Gpu Architecture Kernel Driver, Arm Bifrost Gpu Kernel Driver, Arm Midgard Gpu Kernel Driver, Arm Valhall Gpu Kernel Driver.

## How do I fix CVE-2023-6241?

Apply the vendor's patch.

## Is CVE-2023-6241 being exploited?

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

Public exploit code:

- CVE-2023-6241 for Pixel 8 (github_poc): https://github.com/s1204IT/CVE-2023-6241
- Adaptation of CVE-2023-6241 for Google Pixel 7 from Google Pixel 8 taken from securitylab/SecurityExploits/Android/Mali/CVE_2023_6241 (github_poc): https://github.com/ilGobbo00/CVE-2023-6241-Pixel7_Adaptation

## Other vulnerabilities in Arm Valhall Gpu Kernel Driver

- [CVE-2023-4211](https://insights.sbomify.com/CVE-2023-4211/): Arm Mali GPU Kernel Driver Use-After-Free (medium 5.5, exploited in the wild)
- [CVE-2023-26083](https://insights.sbomify.com/CVE-2023-26083/): Arm Mali GPU Kernel Driver Information Disclosure (low 3.3, exploited in the wild)
- [CVE-2023-6143](https://insights.sbomify.com/CVE-2023-6143/): Mali GPU Kernel Driver allows improper GPU memory processing operations (high 8.4)
- [CVE-2025-0073](https://insights.sbomify.com/CVE-2025-0073/): Mali GPU Kernel Driver allows improper GPU memory processing operations (high 7.8)
- [CVE-2025-0819](https://insights.sbomify.com/CVE-2025-0819/): Mali GPU Kernel Driver allows access to already freed memory (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6241 and fix it if it is affected.

What it is: CVE-2023-6241 is a high-severity use after free vulnerability in Arm Valhall Gpu Kernel Driver, published on 4 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6241 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-2023-6241/ (Markdown: https://insights.sbomify.com/CVE-2023-6241/index.md)
```

## Sources

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

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