# CVE-2025-68747: drm/panthor: Fix UAF on kernel BO VA nodes

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

- **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:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-68747, DEBIAN-CVE-2025-68747, GHSA-348v-47hf-22wr, ROOT-OS-DEBIAN-13-CVE-2025-68747, UBUNTU-CVE-2025-68747

## What is CVE-2025-68747?

CVE-2025-68747 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: Fix UAF on kernel BO VA nodes

If the MMU is down, panthor_vm_unmap_range() might return an error.
We expect the page table to be updated still, and if the MMU is blocked,
the rest of the GPU should be blocked too, so no risk of accessing
physical memory returned to the system (which the current code doesn't
cover for anyway).

Proceed with the rest of the cleanup instead of bailing out and leaving
the va_node inserted in the drm_mm, which leads to UAF when other
adjacent nodes are removed from the drm_mm tree.

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


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

Apply the vendor's patch.

## Is CVE-2025-68747 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68747 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-68747 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-68747/ (Markdown: https://insights.sbomify.com/CVE-2025-68747/index.md)
```

## Sources

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

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