<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 03:38:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54217 — Revert "drm/msm: Add missing check and destroy for alloc_ordered_workqueue"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54217</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Revert &amp;#34;drm/msm: Add missing check and destroy for alloc_ordered_workqueue&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit 643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0.&lt;/p&gt;
&lt;p&gt;A recent patch that tried to fix up the msm_drm_init() paths with
respect to the workqueue but only ended up making things worse:&lt;/p&gt;
&lt;p&gt;First, the newly added calls to msm_drm_uninit() on early errors would
trigger NULL-pointer dereferences, for example, as the kms pointer would
not have been initialised. (Note that these paths were also modified by
a second broken error handling patch which in effect cancelled out this
part when merged.)&lt;/p&gt;
&lt;p&gt;Second, the newly added allocation sanity check would still leak the
previously allocated drm device.&lt;/p&gt;
&lt;p&gt;Instead of trying to salvage what was badly broken (and clearly not
tested), let&amp;#39;s revert the bad commit so that clean and backportable
fixes can be added in its place.&lt;/p&gt;
&lt;p&gt;Patchwork: https://patchwork.freedesktop.org/patch/525107/&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Revert &amp;#34;drm/msm: Add missing check and destroy for alloc_ordered_workqueue&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit 643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0.&lt;/p&gt;
&lt;p&gt;A recent patch that tried to fix up the msm_drm_init() paths with
respect to the workqueue but only ended up making things worse:&lt;/p&gt;
&lt;p&gt;First, the newly added calls to msm_drm_uninit() on early errors would
trigger NULL-pointer dereferences, for example, as the kms pointer would
not have been initialised. (Note that these paths were also modified by
a second broken error handling patch which in effect cancelled out this
part when merged.)&lt;/p&gt;
&lt;p&gt;Second, the newly added allocation sanity check would still leak the
previously allocated drm device.&lt;/p&gt;
&lt;p&gt;Instead of trying to salvage what was badly broken (and clearly not
tested), let&amp;#39;s revert the bad commit so that clean and backportable
fixes can be added in its place.&lt;/p&gt;
&lt;p&gt;Patchwork: https://patchwork.freedesktop.org/patch/525107/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54217</guid>
    </item>
  </channel>
</rss>
