<?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 16:26:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49963 — drm/i915/ttm: fix CCS handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49963</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/i915/ttm: fix CCS handling&lt;/p&gt;
&lt;p&gt;Crucible + recent Mesa seems to sometimes hit:&lt;/p&gt;
&lt;p&gt;GEM_BUG_ON(num_ccs_blks &amp;gt; NUM_CCS_BLKS_PER_XFER)&lt;/p&gt;
&lt;p&gt;And it looks like we can also trigger this with gem_lmem_swapping, if we
modify the test to use slightly larger object sizes.&lt;/p&gt;
&lt;p&gt;Looking closer it looks like we have the following issues in
migrate_copy():&lt;/p&gt;
&lt;p&gt;- We are using plain integer in various places, which we can easily
    overflow with a large object.&lt;/p&gt;
&lt;p&gt;- We pass the entire object size (when the src is lmem) into
    emit_pte() and then try to copy it, which doesn&amp;#39;t work, since we
    only have a few fixed sized windows in which to map the pages and
    perform the copy. With an object &amp;gt; 8M we therefore aren&amp;#39;t properly
    copying the pages. And then with an object &amp;gt; 64M we trigger the
    GEM_BUG_ON(num_ccs_blks &amp;gt; NUM_CCS_BLKS_PER_XFER).&lt;/p&gt;
&lt;p&gt;So it looks like our copy handling for any object &amp;gt; 8M (which is our
CHUNK_SZ) is currently broken on DG2.&lt;/p&gt;
&lt;p&gt;Testcase: igt@gem_lmem_swapping
(cherry picked from commit 8676145eb2f53a9940ff70910caf0125bd8a4bc2)&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/i915/ttm: fix CCS handling&lt;/p&gt;
&lt;p&gt;Crucible + recent Mesa seems to sometimes hit:&lt;/p&gt;
&lt;p&gt;GEM_BUG_ON(num_ccs_blks &amp;gt; NUM_CCS_BLKS_PER_XFER)&lt;/p&gt;
&lt;p&gt;And it looks like we can also trigger this with gem_lmem_swapping, if we
modify the test to use slightly larger object sizes.&lt;/p&gt;
&lt;p&gt;Looking closer it looks like we have the following issues in
migrate_copy():&lt;/p&gt;
&lt;p&gt;- We are using plain integer in various places, which we can easily
    overflow with a large object.&lt;/p&gt;
&lt;p&gt;- We pass the entire object size (when the src is lmem) into
    emit_pte() and then try to copy it, which doesn&amp;#39;t work, since we
    only have a few fixed sized windows in which to map the pages and
    perform the copy. With an object &amp;gt; 8M we therefore aren&amp;#39;t properly
    copying the pages. And then with an object &amp;gt; 64M we trigger the
    GEM_BUG_ON(num_ccs_blks &amp;gt; NUM_CCS_BLKS_PER_XFER).&lt;/p&gt;
&lt;p&gt;So it looks like our copy handling for any object &amp;gt; 8M (which is our
CHUNK_SZ) is currently broken on DG2.&lt;/p&gt;
&lt;p&gt;Testcase: igt@gem_lmem_swapping
(cherry picked from commit 8676145eb2f53a9940ff70910caf0125bd8a4bc2)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49963</guid>
    </item>
  </channel>
</rss>
