# CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation

> A use-after-free vulnerability in the Linux kernel Panthor GPU driver allows local attackers to potentially execute code or escalate privileges via race conditions.

- **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:** 24 Dec 2025
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2025-68735, DEBIAN-CVE-2025-68735, GHSA-cqpf-ph48-g563, ROOT-OS-DEBIAN-13-CVE-2025-68735, UBUNTU-CVE-2025-68735

## What is CVE-2025-68735?

CVE-2025-68735 is a high-severity use after free vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/panthor: Prevent potential UAF in group creation

This commit prevents the possibility of a use after free issue in the
GROUP_CREATE ioctl function, which arose as pointer to the group is
accessed in that ioctl function after storing it in the Xarray.
A malicious userspace can second guess the handle of a group and try
to call GROUP_DESTROY ioctl from another thread around the same time
as GROUP_CREATE ioctl.

To prevent the use after free exploit, this commit uses a mark on an
entry of group pool Xarray which is added just before returning from
the GROUP_CREATE ioctl function. The mark is checked for all ioctls
that specify the group handle and so userspace won't be abe to delete
a group that isn't marked yet.

v2: Add R-bs and fixes tags

## Which versions are affected by CVE-2025-68735?


## How do I fix CVE-2025-68735?

Apply the vendor's patch.

## Is CVE-2025-68735 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68735 and fix it if it is affected.

What it is: CVE-2025-68735 is a high-severity use after free vulnerability in Linux, published on 24 Dec 2025. 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-2025-68735 in the wild and no public exploit code.

Affected product: Linux. 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-2025-68735/ (Markdown: https://insights.sbomify.com/CVE-2025-68735/index.md)
```

## Sources

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

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