<?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 15:41:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46220 — drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46220</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/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission&lt;/p&gt;
&lt;p&gt;sdma_v4_0_ring_emit_fence() contains two BUG_ON(addr &amp;amp; 0x3) assertions
that verify fence writeback addresses are dword-aligned.  These
assertions can be reached from unprivileged userspace via crafted
DRM_IOCTL_AMDGPU_CS submissions, causing a fatal kernel panic in a
scheduler worker thread.&lt;/p&gt;
&lt;p&gt;Replace both BUG_ON() calls with WARN_ON() to log the condition without
crashing the kernel.  A misaligned fence address at this point indicates
a driver bug, but crashing the kernel is never the correct response when
the assertion is reachable from userspace.&lt;/p&gt;
&lt;p&gt;The CS IOCTL path is the correct place to filter invalid submissions;
the ring emission callback is too late to do anything about it.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit b90250bd933afd1ba94d86d6b13821997b22b18e)&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/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission&lt;/p&gt;
&lt;p&gt;sdma_v4_0_ring_emit_fence() contains two BUG_ON(addr &amp;amp; 0x3) assertions
that verify fence writeback addresses are dword-aligned.  These
assertions can be reached from unprivileged userspace via crafted
DRM_IOCTL_AMDGPU_CS submissions, causing a fatal kernel panic in a
scheduler worker thread.&lt;/p&gt;
&lt;p&gt;Replace both BUG_ON() calls with WARN_ON() to log the condition without
crashing the kernel.  A misaligned fence address at this point indicates
a driver bug, but crashing the kernel is never the correct response when
the assertion is reachable from userspace.&lt;/p&gt;
&lt;p&gt;The CS IOCTL path is the correct place to filter invalid submissions;
the ring emission callback is too late to do anything about it.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit b90250bd933afd1ba94d86d6b13821997b22b18e)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46220</guid>
    </item>
  </channel>
</rss>
