<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T23:35:09.771957+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-93058</id>
    <title>CVE-2026-93058 — drm/msm: Only fini scheduler after successful init</title>
    <updated>2026-09-30T23:35:09.773627+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/msm: Only fini scheduler after successful init</p>
<p>msm_ringbuffer_new() destroys a partially initialized ring through
msm_ringbuffer_destroy() when an allocation or scheduler setup step
fails.</p>
<p>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.</p>
<p>Track successful scheduler initialization and call drm_sched_fini() only
after drm_sched_init() returned 0.</p>
<p>This issue was found by a static analysis checker and confirmed by
manual source review.</p>
<p>Patchwork: https://patchwork.freedesktop.org/patch/738905/</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-93058"/>
  </entry>
</feed>
