<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:31:27 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99630</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99630</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu/userq: validate the moved individual BOs on restore&lt;/p&gt;
&lt;p&gt;An individual BO of a user queue VM, i.e. one which doesn&amp;#39;t share the
root reservation, goes to the individual needs_update list when it is
evicted. The user queue restore looked at vm-&amp;gt;invalidated for them, which
the VM state machine rework turned into the always_valid evicted list and
commit 18decfc9e8cc (&amp;#34;drm/amdgpu/userq: actually validate userq BOs&amp;#34;)
into the individual evicted one. That list only holds imported DMA-bufs of
compute VMs though, so for a user queue VM nothing is validated.&lt;/p&gt;
&lt;p&gt;The restore then neither locks such a BO nor moves it back. Its PTEs are
updated to wherever it is now, cleared if it went to system memory, and
it doesn&amp;#39;t get the new eviction fence, so it can move again under the
running queue.&lt;/p&gt;
&lt;p&gt;On navi48, once the BOs of an SDMA user queue are evicted from GTT
(debugfs amdgpu_evict_gtt) the queue faults on its ring and rptr:&lt;/p&gt;
&lt;p&gt;amdgpu 0000:03:00.0:   in page starting at address 0x0000000100000000 from client 10
  amdgpu 0000:03:00.0: 	 Faulty UTCL2 client ID: SDMA0 (0xd)
  amdgpu 0000:03:00.0:   in page starting at address 0x0000000100101000 from client 10&lt;/p&gt;
&lt;p&gt;Validate the BOs on the individual needs_update list like before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu/userq: validate the moved individual BOs on restore&lt;/p&gt;
&lt;p&gt;An individual BO of a user queue VM, i.e. one which doesn&amp;#39;t share the
root reservation, goes to the individual needs_update list when it is
evicted. The user queue restore looked at vm-&amp;gt;invalidated for them, which
the VM state machine rework turned into the always_valid evicted list and
commit 18decfc9e8cc (&amp;#34;drm/amdgpu/userq: actually validate userq BOs&amp;#34;)
into the individual evicted one. That list only holds imported DMA-bufs of
compute VMs though, so for a user queue VM nothing is validated.&lt;/p&gt;
&lt;p&gt;The restore then neither locks such a BO nor moves it back. Its PTEs are
updated to wherever it is now, cleared if it went to system memory, and
it doesn&amp;#39;t get the new eviction fence, so it can move again under the
running queue.&lt;/p&gt;
&lt;p&gt;On navi48, once the BOs of an SDMA user queue are evicted from GTT
(debugfs amdgpu_evict_gtt) the queue faults on its ring and rptr:&lt;/p&gt;
&lt;p&gt;amdgpu 0000:03:00.0:   in page starting at address 0x0000000100000000 from client 10
  amdgpu 0000:03:00.0: 	 Faulty UTCL2 client ID: SDMA0 (0xd)
  amdgpu 0000:03:00.0:   in page starting at address 0x0000000100101000 from client 10&lt;/p&gt;
&lt;p&gt;Validate the BOs on the individual needs_update list like before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99630</guid>
    </item>
    <item>
      <title>GHSA-44g4-x938-29mr</title>
      <link>https://db.gcve.eu/vuln/ghsa-44g4-x938-29mr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu/userq: validate the moved individual BOs on restore&lt;/p&gt;
&lt;p&gt;An individual BO of a user queue VM, i.e. one which doesn&amp;#39;t share the
root reservation, goes to the individual needs_update list when it is
evicted. The user queue restore looked at vm-&amp;gt;invalidated for them, which
the VM state machine rework turned into the always_valid evicted list and
commit 18decfc9e8cc (&amp;#34;drm/amdgpu/userq: actually validate userq BOs&amp;#34;)
into the individual evicted one. That list only holds imported DMA-bufs of
compute VMs though, so for a user queue VM nothing is validated.&lt;/p&gt;
&lt;p&gt;The restore then neither locks such a BO nor moves it back. Its PTEs are
updated to wherever it is now, cleared if it went to system memory, and
it doesn&amp;#39;t get the new eviction fence, so it can move again under the
running queue.&lt;/p&gt;
&lt;p&gt;On navi48, once the BOs of an SDMA user queue are evicted from GTT
(debugfs amdgpu_evict_gtt) the queue faults on its ring and rptr:&lt;/p&gt;
&lt;p&gt;amdgpu 0000:03:00.0:   in page starting at address 0x0000000100000000 from client 10
  amdgpu 0000:03:00.0: 	 Faulty UTCL2 client ID: SDMA0 (0xd)
  amdgpu 0000:03:00.0:   in page starting at address 0x0000000100101000 from client 10&lt;/p&gt;
&lt;p&gt;Validate the BOs on the individual needs_update list like before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu/userq: validate the moved individual BOs on restore&lt;/p&gt;
&lt;p&gt;An individual BO of a user queue VM, i.e. one which doesn&amp;#39;t share the
root reservation, goes to the individual needs_update list when it is
evicted. The user queue restore looked at vm-&amp;gt;invalidated for them, which
the VM state machine rework turned into the always_valid evicted list and
commit 18decfc9e8cc (&amp;#34;drm/amdgpu/userq: actually validate userq BOs&amp;#34;)
into the individual evicted one. That list only holds imported DMA-bufs of
compute VMs though, so for a user queue VM nothing is validated.&lt;/p&gt;
&lt;p&gt;The restore then neither locks such a BO nor moves it back. Its PTEs are
updated to wherever it is now, cleared if it went to system memory, and
it doesn&amp;#39;t get the new eviction fence, so it can move again under the
running queue.&lt;/p&gt;
&lt;p&gt;On navi48, once the BOs of an SDMA user queue are evicted from GTT
(debugfs amdgpu_evict_gtt) the queue faults on its ring and rptr:&lt;/p&gt;
&lt;p&gt;amdgpu 0000:03:00.0:   in page starting at address 0x0000000100000000 from client 10
  amdgpu 0000:03:00.0: 	 Faulty UTCL2 client ID: SDMA0 (0xd)
  amdgpu 0000:03:00.0:   in page starting at address 0x0000000100101000 from client 10&lt;/p&gt;
&lt;p&gt;Validate the BOs on the individual needs_update list like before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-44g4-x938-29mr</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
