# CVE-2026-99095: drm/vc4: drain the hangcheck timer and works on V3D unbind


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-111128, BELL-CVE-2026-99095, DEBIAN-CVE-2026-99095, GHSA-v4rc-4368-fvrr, UBUNTU-CVE-2026-99095

## What is CVE-2026-99095?

CVE-2026-99095 is a vulnerability in Linux, published on 26 Oct 2026. 

### Official description

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

drm/vc4: drain the hangcheck timer and works on V3D unbind

Nothing stops the hangcheck timer that submitted jobs arm, or the
job_done_work that the render-done interrupt queues, at teardown:
vc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy()
runs from the drm-managed release, after vc4_v3d_unbind() has already
uninstalled the V3D interrupt and cleared vc4->v3d. A timer still armed
by then reads V3D registers through the NULL vc4->v3d pointer, and the
late callbacks run on the vc4_dev embedding them after it has been
freed.

Drain them in vc4_v3d_unbind(): shut the timer down and cancel
reset_work before the interrupt is taken down, because its
vc4_irq_reset() re-enables it, then flush job_done_work so that
completions queued at teardown still release their jobs.

This issue was found by an in-house static analysis tool.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99095 is a vulnerability in Linux, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99095 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-99095/ (Markdown: https://insights.sbomify.com/CVE-2026-99095/index.md)
```

## Sources

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

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