GHSA-2M9V-9VX7-P7W7
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
drm/msm: Only fini scheduler after successful init
msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails.
If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized.
Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0.
This issue was found by a static analysis checker and confirmed by manual source review.
Patchwork: https://patchwork.freedesktop.org/patch/738905/
{
"affected": [],
"aliases": [
"CVE-2026-93058"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:59Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm: Only fini scheduler after successful init\n\nmsm_ringbuffer_new() destroys a partially initialized ring through\nmsm_ringbuffer_destroy() when an allocation or scheduler setup step\nfails.\n\nIf drm_sched_init() fails before it finishes initializing the scheduler,\nthe failure path still calls drm_sched_fini(). That teardown path assumes\nthe scheduler work items, lists, and workqueue state were initialized.\n\nTrack successful scheduler initialization and call drm_sched_fini() only\nafter drm_sched_init() returned 0.\n\nThis issue was found by a static analysis checker and confirmed by\nmanual source review.\n\nPatchwork: https://patchwork.freedesktop.org/patch/738905/",
"id": "GHSA-2m9v-9vx7-p7w7",
"modified": "2026-09-17T18:32:08Z",
"published": "2026-09-17T18:32:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93058"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/09b360eb6ce345996a30fad8c86e9df80f41cd7e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d43e1bbfd43458b9242806eec77ea3b032134baf"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e2332abed2a4d3caa59052095dc16e4ce44791ea"
}
],
"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.