# CVE-2026-72388: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock

> A race condition in the Panthor GPU driver can cause a kernel deadlock or crash when fence locks are accessed from interrupt context.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-72388, DEBIAN-CVE-2026-72388, GHSA-2vh6-fvwq-hq8w, UBUNTU-CVE-2026-72388

## What is CVE-2026-72388?

CVE-2026-72388 is a vulnerability in Linux, published on 15 Aug 2026. 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: Always use the IRQ-safe variant when acquiring the fence lock

Since dma_fence objects can be shared with other subsystems, they may be
accessed from hardirq context in those drivers, and we have to take
that into account by also using the IRQ-safe variant when acquiring
the lock.

While at it, switch to the guard model.

## Which versions are affected by CVE-2026-72388?


## How do I fix CVE-2026-72388?

Apply the vendor's patch.

## Is CVE-2026-72388 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72388 and fix it if it is affected.

What it is: CVE-2026-72388 is a vulnerability in Linux, published on 15 Aug 2026. 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-2026-72388 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-2026-72388/ (Markdown: https://insights.sbomify.com/CVE-2026-72388/index.md)
```

## Sources

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

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