Answer in brief
CVE-2026-93058 records a Unknown severity vulnerability in drm/msm: Only fini scheduler after successful init. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 <d43e1bbfd43458b9242806eec77ea3b032134baf || >=1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 <09b360eb6ce345996a30fad8c86e9df80f41cd7e || >=1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 <e2332abed2a4d3caa59052095dc16e4ce44791ea | d43e1bbfd43458b9242806eec77ea3b032134baf, 09b360eb6ce345996a30fad8c86e9df80f41cd7e, e2332abed2a4d3caa59052095dc16e4ce44791ea |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
In 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/
Quoted source text, attributed separately from HOL analysis.