# CVE-2026-89590: accel/rocket: Fix error path handling in rocket_job_run()

> A local attacker can trigger a resource leak in the Rocket NPU driver, preventing device suspension and causing a denial of service.

- **Severity:** Not scored
- **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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89590, DEBIAN-CVE-2026-89590, GHSA-8m8f-887v-xxcc, UBUNTU-CVE-2026-89590

## What is CVE-2026-89590?

CVE-2026-89590 is a denial of service vulnerability in Linux, published on 11 Sep 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:

accel/rocket: Fix error path handling in rocket_job_run()

In rocket_job_run(), after taking an extra fence reference for
job->done_fence via dma_fence_get(), the error paths have three bugs:

- The dma_fence reference held by job->done_fence is never released,
  causing a reference leak.
- pm_runtime_get_sync() increments the usage counter even on failure,
  but the error path does not decrement it, leaking the runtime PM
  reference and preventing the NPU from suspending.
- A valid but unsignaled fence is returned to the DRM scheduler,
  which triggers WARN("Fence ... released with pending signals!")
  when the scheduler drops its reference.

Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get()
which auto-balances the usage counter on failure, releasing both fence
references on error, and returning ERR_PTR(ret) instead of the
unsignaled fence.

[tomeu: Refactored error paths to use consolidated goto labels]

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


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

Apply the vendor's patch.

## Is CVE-2026-89590 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89590 is a denial of service vulnerability in Linux, published on 11 Sep 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-89590 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-89590/ (Markdown: https://insights.sbomify.com/CVE-2026-89590/index.md)
```

## Sources

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

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