GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-8M8F-887V-XXCC

Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31
VLAI
Details

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]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-89590"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-11T20:19:43Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/rocket: Fix error path handling in rocket_job_run()\n\nIn rocket_job_run(), after taking an extra fence reference for\njob-\u003edone_fence via dma_fence_get(), the error paths have three bugs:\n\n- The dma_fence reference held by job-\u003edone_fence is never released,\n  causing a reference leak.\n- pm_runtime_get_sync() increments the usage counter even on failure,\n  but the error path does not decrement it, leaking the runtime PM\n  reference and preventing the NPU from suspending.\n- A valid but unsignaled fence is returned to the DRM scheduler,\n  which triggers WARN(\"Fence ... released with pending signals!\")\n  when the scheduler drops its reference.\n\nFix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get()\nwhich auto-balances the usage counter on failure, releasing both fence\nreferences on error, and returning ERR_PTR(ret) instead of the\nunsignaled fence.\n\n[tomeu: Refactored error paths to use consolidated goto labels]",
  "id": "GHSA-8m8f-887v-xxcc",
  "modified": "2026-09-11T21:31:33Z",
  "published": "2026-09-11T21:31:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89590"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7d6fa298c23495b805004f5f446497b661998fa5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9ad8821573a36bcd18c84dbca3027802b0ea062f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9b2dedadf6a91ac3fc9fae268bb556a041222711"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…