GHSA-PP5J-W2PR-XVV3
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In the Linux kernel, the following vulnerability has been resolved:
accel/rocket: initialize job domain before cleanup paths
rocket_ioctl_submit_job() releases rjob through rocket_job_put() on allocation error paths. rocket_job_cleanup() unconditionally calls rocket_iommu_domain_put(job->domain), but job->domain is assigned only after task copying and BO lookups. A failure before that assignment can therefore clean up a job with a NULL domain pointer.
Take the per-file domain reference before the first error path can release rjob. Also clear rjob->tasks after freeing it in rocket_copy_tasks(), so the common cleanup path cannot free the task array again after a task-copy error.
{
"affected": [],
"aliases": [
"CVE-2026-89591"
],
"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: initialize job domain before cleanup paths\n\nrocket_ioctl_submit_job() releases rjob through rocket_job_put() on\nallocation error paths. rocket_job_cleanup() unconditionally calls\nrocket_iommu_domain_put(job-\u003edomain), but job-\u003edomain is assigned only\nafter task copying and BO lookups. A failure before that assignment can\ntherefore clean up a job with a NULL domain pointer.\n\nTake the per-file domain reference before the first error path can release\nrjob. Also clear rjob-\u003etasks after freeing it in rocket_copy_tasks(), so\nthe common cleanup path cannot free the task array again after a task-copy\nerror.",
"id": "GHSA-pp5j-w2pr-xvv3",
"modified": "2026-09-11T21:31:33Z",
"published": "2026-09-11T21:31:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89591"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3043230296653a609ab50006899e64bbb2d99465"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/70e6a33d68a9b03335c5426332666e52d07f45d6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/81731f1eda5e6a1dfad31445f741de9bbefbb08e"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.