<?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://cve.radiocsirt.org</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, 07 Oct 2026 23:56:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-27400 — drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-27400</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: once more fix the call oder in amdgpu_ttm_move() v2&lt;/p&gt;
&lt;p&gt;This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move
on same heap. The basic problem here is that after the move the old
location is simply not available any more.&lt;/p&gt;
&lt;p&gt;Some fixes were suggested, but essentially we should call the move
notification before actually moving things because only this way we have
the correct order for DMA-buf and VM move notifications as well.&lt;/p&gt;
&lt;p&gt;Also rework the statistic handling so that we don&amp;#39;t update the eviction
counter before the move.&lt;/p&gt;
&lt;p&gt;v2: add missing NULL check&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: once more fix the call oder in amdgpu_ttm_move() v2&lt;/p&gt;
&lt;p&gt;This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move
on same heap. The basic problem here is that after the move the old
location is simply not available any more.&lt;/p&gt;
&lt;p&gt;Some fixes were suggested, but essentially we should call the move
notification before actually moving things because only this way we have
the correct order for DMA-buf and VM move notifications as well.&lt;/p&gt;
&lt;p&gt;Also rework the statistic handling so that we don&amp;#39;t update the eviction
counter before the move.&lt;/p&gt;
&lt;p&gt;v2: add missing NULL check&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-27400</guid>
    </item>
  </channel>
</rss>
