<?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>Wed, 30 Sep 2026 01:24:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68236 — drm/amd/display: set new_stream to NULL after release</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68236</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;drm/amd/display: set new_stream to NULL after release&lt;/p&gt;
&lt;p&gt;In dm_update_crtc_state(), the skip_modeset path releases new_stream
via dc_stream_release() but does not set the pointer to NULL.&lt;/p&gt;
&lt;p&gt;If a later error (e.g., color management failure) triggers the fail
label, the error path calls dc_stream_release() again on the same
dangling pointer, causing a double release and potential use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by setting new_stream to NULL after the initial release.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 99f3af19073b3ddbfd96e789124cce12c4277b28)&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;drm/amd/display: set new_stream to NULL after release&lt;/p&gt;
&lt;p&gt;In dm_update_crtc_state(), the skip_modeset path releases new_stream
via dc_stream_release() but does not set the pointer to NULL.&lt;/p&gt;
&lt;p&gt;If a later error (e.g., color management failure) triggers the fail
label, the error path calls dc_stream_release() again on the same
dangling pointer, causing a double release and potential use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by setting new_stream to NULL after the initial release.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 99f3af19073b3ddbfd96e789124cce12c4277b28)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68236</guid>
    </item>
  </channel>
</rss>
