Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93058

drm/msm: Only fini scheduler after successful init

Description

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/

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 – < 20ea0ae8e90702acca83467207db4c9bd8c8bd03
    • affected 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 – < bd2a5a876904eaf688a093cd73986abc3571f26b
    • affected 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 – < aafc9258efeec98fcb7e3998356b4b25bf1ad159
    • affected 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 – < d43e1bbfd43458b9242806eec77ea3b032134baf
    • affected 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 – < 09b360eb6ce345996a30fad8c86e9df80f41cd7e
    • affected 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 – < e2332abed2a4d3caa59052095dc16e4ce44791ea
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93058 badge
[![CVE-2026-93058](https://cveledger.app/badge/CVE-2026-93058.svg)](https://cveledger.app/cve/CVE-2026-93058)

Record last updated .