<?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:05:50 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99631</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99631</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: check amdgpu_vm_ready() in dma-buf move notify&lt;/p&gt;
&lt;p&gt;amdgpu_dma_buf_move_notify() touches the page tables without first
calling amdgpu_vm_ready(). When a process is SIGKILLed, its VM entities
are stopped. Teardown of an imported dma-buf then tries to clear PTEs by
submitting to one of those stopped entities. That eventually hangs the
task.&lt;/p&gt;
&lt;p&gt;Commit aa5fc4362fac (&amp;#34;drm/amdgpu: fix task hang from failed job
submission during process kill&amp;#34;) added the stopped entity check in
amdgpu_vm_ready() and used it in amdgpu_cs_vm_handling(). That did not
cover a call in amdgpu_dma_buf_move_notify(), what was already mentioned
in:
https://lists.freedesktop.org/archives/amd-gfx/2025-October/133076.html&lt;/p&gt;
&lt;p&gt;Tested by SIGKILLing a GPU workload holding imported dma-bufs. Without
the patch &amp;#34;Trying to push to a killed entity&amp;#34; errors are logged, then a
task hangs. With the patch there are no hung tasks. This was tested on a
6.18 kernel.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit bee5c9d7a34cb1b510ad3b4c18c30f9d38b0ab7d)&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: check amdgpu_vm_ready() in dma-buf move notify&lt;/p&gt;
&lt;p&gt;amdgpu_dma_buf_move_notify() touches the page tables without first
calling amdgpu_vm_ready(). When a process is SIGKILLed, its VM entities
are stopped. Teardown of an imported dma-buf then tries to clear PTEs by
submitting to one of those stopped entities. That eventually hangs the
task.&lt;/p&gt;
&lt;p&gt;Commit aa5fc4362fac (&amp;#34;drm/amdgpu: fix task hang from failed job
submission during process kill&amp;#34;) added the stopped entity check in
amdgpu_vm_ready() and used it in amdgpu_cs_vm_handling(). That did not
cover a call in amdgpu_dma_buf_move_notify(), what was already mentioned
in:
https://lists.freedesktop.org/archives/amd-gfx/2025-October/133076.html&lt;/p&gt;
&lt;p&gt;Tested by SIGKILLing a GPU workload holding imported dma-bufs. Without
the patch &amp;#34;Trying to push to a killed entity&amp;#34; errors are logged, then a
task hangs. With the patch there are no hung tasks. This was tested on a
6.18 kernel.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit bee5c9d7a34cb1b510ad3b4c18c30f9d38b0ab7d)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99631</guid>
    </item>
    <item>
      <title>GHSA-fhfj-f8gw-f5mp</title>
      <link>https://db.gcve.eu/vuln/ghsa-fhfj-f8gw-f5mp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: check amdgpu_vm_ready() in dma-buf move notify&lt;/p&gt;
&lt;p&gt;amdgpu_dma_buf_move_notify() touches the page tables without first
calling amdgpu_vm_ready(). When a process is SIGKILLed, its VM entities
are stopped. Teardown of an imported dma-buf then tries to clear PTEs by
submitting to one of those stopped entities. That eventually hangs the
task.&lt;/p&gt;
&lt;p&gt;Commit aa5fc4362fac (&amp;#34;drm/amdgpu: fix task hang from failed job
submission during process kill&amp;#34;) added the stopped entity check in
amdgpu_vm_ready() and used it in amdgpu_cs_vm_handling(). That did not
cover a call in amdgpu_dma_buf_move_notify(), what was already mentioned
in:
https://lists.freedesktop.org/archives/amd-gfx/2025-October/133076.html&lt;/p&gt;
&lt;p&gt;Tested by SIGKILLing a GPU workload holding imported dma-bufs. Without
the patch &amp;#34;Trying to push to a killed entity&amp;#34; errors are logged, then a
task hangs. With the patch there are no hung tasks. This was tested on a
6.18 kernel.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit bee5c9d7a34cb1b510ad3b4c18c30f9d38b0ab7d)&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: check amdgpu_vm_ready() in dma-buf move notify&lt;/p&gt;
&lt;p&gt;amdgpu_dma_buf_move_notify() touches the page tables without first
calling amdgpu_vm_ready(). When a process is SIGKILLed, its VM entities
are stopped. Teardown of an imported dma-buf then tries to clear PTEs by
submitting to one of those stopped entities. That eventually hangs the
task.&lt;/p&gt;
&lt;p&gt;Commit aa5fc4362fac (&amp;#34;drm/amdgpu: fix task hang from failed job
submission during process kill&amp;#34;) added the stopped entity check in
amdgpu_vm_ready() and used it in amdgpu_cs_vm_handling(). That did not
cover a call in amdgpu_dma_buf_move_notify(), what was already mentioned
in:
https://lists.freedesktop.org/archives/amd-gfx/2025-October/133076.html&lt;/p&gt;
&lt;p&gt;Tested by SIGKILLing a GPU workload holding imported dma-bufs. Without
the patch &amp;#34;Trying to push to a killed entity&amp;#34; errors are logged, then a
task hangs. With the patch there are no hung tasks. This was tested on a
6.18 kernel.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit bee5c9d7a34cb1b510ad3b4c18c30f9d38b0ab7d)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fhfj-f8gw-f5mp</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>
