VulnerabilityPublished 17 Sep 2026Updated 30 Oct 2026

CVE-2026-93058: Linux kernel · drm/msm: Only fini scheduler after successful init

Source GCVE Database

Compare

Authoritative record:CVE-2026-93058

Not known to be exploited · fixed in e2332abed2a4d3caa59052095dc16e4ce44791ea : update Linux kernel when convenient.

Data as of 30 Oct 2026, 18:18 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in e2332abed2a4d3caa59052095dc16e4ce44791ea, d43e1bbfd43458b9242806eec77ea3b032134baf, bd2a5a876904eaf688a093cd73986abc3571f26b +3

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-2m9v-9vx7-p7w7

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < e2332abed2a4d3caa59052095dc16e4ce44791ea	Fixed in e2332abed2a4d3caa59052095dc16e4ce44791ea
LinuxLinux	Affected ≥ 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < d43e1bbfd43458b9242806eec77ea3b032134baf	Fixed in d43e1bbfd43458b9242806eec77ea3b032134baf
LinuxLinux	Affected ≥ 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < bd2a5a876904eaf688a093cd73986abc3571f26b	Fixed in bd2a5a876904eaf688a093cd73986abc3571f26b
LinuxLinux	Affected ≥ 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < aafc9258efeec98fcb7e3998356b4b25bf1ad159	Fixed in aafc9258efeec98fcb7e3998356b4b25bf1ad159
LinuxLinux	Affected ≥ 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < 20ea0ae8e90702acca83467207db4c9bd8c8bd03	Fixed in 20ea0ae8e90702acca83467207db4c9bd8c8bd03
LinuxLinux	Affected ≥ 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < 09b360eb6ce345996a30fad8c86e9df80f41cd7e	Fixed in 09b360eb6ce345996a30fad8c86e9df80f41cd7e

AI-suggested

A patch has been applied to ensure drm_sched_fini() is only called after successful scheduler initialization. Users should update their Linux kernel to a version including this fix once available. Until then, no specific workaround is documented.

Description

A flaw in the Linux kernel's drm/msm driver caused improper cleanup of the scheduler when initialization failed. Specifically, drm_sched_fini() was called even if drm_sched_init() did not complete successfully, leading to teardown operations on uninitialized scheduler components. This issue was identified through static analysis and manual review and has been fixed by ensuring drm_sched_fini() is only called after successful scheduler initialization.

Impact

The vulnerability may cause kernel instability or crashes due to teardown operations on uninitialized scheduler structures. There is no indication of privilege escalation or information disclosure. No known exploits in the wild have been reported.

Summary

The vulnerability in the Linux kernel's drm/msm component involves the improper handling of scheduler teardown during failure paths. When drm_sched_init() fails before completing scheduler initialization, drm_sched_fini() is still called, which assumes that scheduler work items, lists, and workqueue states were initialized. This can lead to undefined behavior or potential kernel instability. The fix tracks successful scheduler initialization and calls drm_sched_fini() only if drm_sched_init() returns success (0). The issue was discovered via static analysis and confirmed by manual source code review.

References

Community reviews

Loading reviews…