<?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:03:41 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99622</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99622</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: drop the dma-buf reference when a KFD import fails&lt;/p&gt;
&lt;p&gt;import_obj_create() takes a reference on the dma-buf for the new kgd_mem,
but the error path after validating the BO doesn&amp;#39;t drop it. Since the
validation reserves the BO interruptibly, an import failing with
-ERESTARTSYS leaks the exported BO with its memory, and keeps the module
in use.&lt;/p&gt;
&lt;p&gt;Importing a 64 MiB VRAM BO in a loop while getting SIGUSR1
every 20 us and another thread changes the BO&amp;#39;s mappings:&lt;/p&gt;
&lt;p&gt;INFO: 171821 imports, VRAM used before 65 MiB, after 129 MiB
  modprobe: FATAL: Module amdgpu is in use.&lt;/p&gt;
&lt;p&gt;Drop the reference, and free the sync object and the mutex of the kgd_mem
as well. With that VRAM usage returns to 65 MiB after the same test.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit b4d1eca2729840148ff2ea957724ce764ca5a94e)&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: drop the dma-buf reference when a KFD import fails&lt;/p&gt;
&lt;p&gt;import_obj_create() takes a reference on the dma-buf for the new kgd_mem,
but the error path after validating the BO doesn&amp;#39;t drop it. Since the
validation reserves the BO interruptibly, an import failing with
-ERESTARTSYS leaks the exported BO with its memory, and keeps the module
in use.&lt;/p&gt;
&lt;p&gt;Importing a 64 MiB VRAM BO in a loop while getting SIGUSR1
every 20 us and another thread changes the BO&amp;#39;s mappings:&lt;/p&gt;
&lt;p&gt;INFO: 171821 imports, VRAM used before 65 MiB, after 129 MiB
  modprobe: FATAL: Module amdgpu is in use.&lt;/p&gt;
&lt;p&gt;Drop the reference, and free the sync object and the mutex of the kgd_mem
as well. With that VRAM usage returns to 65 MiB after the same test.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit b4d1eca2729840148ff2ea957724ce764ca5a94e)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99622</guid>
    </item>
    <item>
      <title>GHSA-7vg7-fqgf-94j5</title>
      <link>https://db.gcve.eu/vuln/ghsa-7vg7-fqgf-94j5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: drop the dma-buf reference when a KFD import fails&lt;/p&gt;
&lt;p&gt;import_obj_create() takes a reference on the dma-buf for the new kgd_mem,
but the error path after validating the BO doesn&amp;#39;t drop it. Since the
validation reserves the BO interruptibly, an import failing with
-ERESTARTSYS leaks the exported BO with its memory, and keeps the module
in use.&lt;/p&gt;
&lt;p&gt;Importing a 64 MiB VRAM BO in a loop while getting SIGUSR1
every 20 us and another thread changes the BO&amp;#39;s mappings:&lt;/p&gt;
&lt;p&gt;INFO: 171821 imports, VRAM used before 65 MiB, after 129 MiB
  modprobe: FATAL: Module amdgpu is in use.&lt;/p&gt;
&lt;p&gt;Drop the reference, and free the sync object and the mutex of the kgd_mem
as well. With that VRAM usage returns to 65 MiB after the same test.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit b4d1eca2729840148ff2ea957724ce764ca5a94e)&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: drop the dma-buf reference when a KFD import fails&lt;/p&gt;
&lt;p&gt;import_obj_create() takes a reference on the dma-buf for the new kgd_mem,
but the error path after validating the BO doesn&amp;#39;t drop it. Since the
validation reserves the BO interruptibly, an import failing with
-ERESTARTSYS leaks the exported BO with its memory, and keeps the module
in use.&lt;/p&gt;
&lt;p&gt;Importing a 64 MiB VRAM BO in a loop while getting SIGUSR1
every 20 us and another thread changes the BO&amp;#39;s mappings:&lt;/p&gt;
&lt;p&gt;INFO: 171821 imports, VRAM used before 65 MiB, after 129 MiB
  modprobe: FATAL: Module amdgpu is in use.&lt;/p&gt;
&lt;p&gt;Drop the reference, and free the sync object and the mutex of the kgd_mem
as well. With that VRAM usage returns to 65 MiB after the same test.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit b4d1eca2729840148ff2ea957724ce764ca5a94e)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7vg7-fqgf-94j5</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>
