<?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 07:29:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46896 — drm/amdgpu: don't access invalid sched</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46896</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: don&amp;#39;t access invalid sched&lt;/p&gt;
&lt;p&gt;Since 2320c9e6a768 (&amp;#34;drm/sched: memset() &amp;#39;job&amp;#39; in drm_sched_job_init()&amp;#34;)
accessing job-&amp;gt;base.sched can produce unexpected results as the initialisation
of (*job)-&amp;gt;base.sched done in amdgpu_job_alloc is overwritten by the
memset.&lt;/p&gt;
&lt;p&gt;This commit fixes an issue when a CS would fail validation and would
be rejected after job-&amp;gt;num_ibs is incremented. In this case,
amdgpu_ib_free(ring-&amp;gt;adev, ...) will be called, which would crash the
machine because the ring value is bogus.&lt;/p&gt;
&lt;p&gt;To fix this, pass a NULL pointer to amdgpu_ib_free(): we can do this
because the device is actually not used in this function.&lt;/p&gt;
&lt;p&gt;The next commit will remove the ring argument completely.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 2ae520cb12831d264ceb97c61f72c59d33c0dbd7)&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: don&amp;#39;t access invalid sched&lt;/p&gt;
&lt;p&gt;Since 2320c9e6a768 (&amp;#34;drm/sched: memset() &amp;#39;job&amp;#39; in drm_sched_job_init()&amp;#34;)
accessing job-&amp;gt;base.sched can produce unexpected results as the initialisation
of (*job)-&amp;gt;base.sched done in amdgpu_job_alloc is overwritten by the
memset.&lt;/p&gt;
&lt;p&gt;This commit fixes an issue when a CS would fail validation and would
be rejected after job-&amp;gt;num_ibs is incremented. In this case,
amdgpu_ib_free(ring-&amp;gt;adev, ...) will be called, which would crash the
machine because the ring value is bogus.&lt;/p&gt;
&lt;p&gt;To fix this, pass a NULL pointer to amdgpu_ib_free(): we can do this
because the device is actually not used in this function.&lt;/p&gt;
&lt;p&gt;The next commit will remove the ring argument completely.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 2ae520cb12831d264ceb97c61f72c59d33c0dbd7)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46896</guid>
    </item>
  </channel>
</rss>
