<?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>Tue, 06 Oct 2026 11:08:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06992</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06992</link>
      <description>bdu:2024-06992</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06992</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26912</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26912</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-26912</guid>
    </item>
    <item>
      <title>EUVD-2026-312648</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312648</link>
      <description>EUVD-2026-312648</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312648</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26912</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26912</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/nouveau: fix several DMA buffer leaks&lt;/p&gt;
&lt;p&gt;Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects.  Several of
these buffers are never dealloced.  Some of them can be deallocated
right after GSP-RM is initialized, but the rest need to stay until the
driver unloads.&lt;/p&gt;
&lt;p&gt;Also futher bullet-proof these objects by poisoning the buffer and
clearing the nvkm_gsp_mem object when it is deallocated.  Poisoning
the buffer should trigger an error (or crash) from GSP-RM if it tries
to access the buffer after we&amp;#39;ve deallocated it, because we were wrong
about when it is safe to deallocate.&lt;/p&gt;
&lt;p&gt;Finally, change the mem-&amp;gt;size field to a size_t because that&amp;#39;s the same
type that dma_alloc_coherent expects.&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/nouveau: fix several DMA buffer leaks&lt;/p&gt;
&lt;p&gt;Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects.  Several of
these buffers are never dealloced.  Some of them can be deallocated
right after GSP-RM is initialized, but the rest need to stay until the
driver unloads.&lt;/p&gt;
&lt;p&gt;Also futher bullet-proof these objects by poisoning the buffer and
clearing the nvkm_gsp_mem object when it is deallocated.  Poisoning
the buffer should trigger an error (or crash) from GSP-RM if it tries
to access the buffer after we&amp;#39;ve deallocated it, because we were wrong
about when it is safe to deallocate.&lt;/p&gt;
&lt;p&gt;Finally, change the mem-&amp;gt;size field to a size_t because that&amp;#39;s the same
type that dma_alloc_coherent expects.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26912</guid>
    </item>
    <item>
      <title>GHSA-v68j-ghq9-ffvc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v68j-ghq9-ffvc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/nouveau: fix several DMA buffer leaks&lt;/p&gt;
&lt;p&gt;Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects.  Several of
these buffers are never dealloced.  Some of them can be deallocated
right after GSP-RM is initialized, but the rest need to stay until the
driver unloads.&lt;/p&gt;
&lt;p&gt;Also futher bullet-proof these objects by poisoning the buffer and
clearing the nvkm_gsp_mem object when it is deallocated.  Poisoning
the buffer should trigger an error (or crash) from GSP-RM if it tries
to access the buffer after we&amp;#39;ve deallocated it, because we were wrong
about when it is safe to deallocate.&lt;/p&gt;
&lt;p&gt;Finally, change the mem-&amp;gt;size field to a size_t because that&amp;#39;s the same
type that dma_alloc_coherent expects.&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/nouveau: fix several DMA buffer leaks&lt;/p&gt;
&lt;p&gt;Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects.  Several of
these buffers are never dealloced.  Some of them can be deallocated
right after GSP-RM is initialized, but the rest need to stay until the
driver unloads.&lt;/p&gt;
&lt;p&gt;Also futher bullet-proof these objects by poisoning the buffer and
clearing the nvkm_gsp_mem object when it is deallocated.  Poisoning
the buffer should trigger an error (or crash) from GSP-RM if it tries
to access the buffer after we&amp;#39;ve deallocated it, because we were wrong
about when it is safe to deallocate.&lt;/p&gt;
&lt;p&gt;Finally, change the mem-&amp;gt;size field to a size_t because that&amp;#39;s the same
type that dma_alloc_coherent expects.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v68j-ghq9-ffvc</guid>
    </item>
    <item>
      <title>gsd-2024-26912</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26912</link>
      <description>gsd-2024-26912</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26912</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26912</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26912</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 56 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix several DMA buffer leaks Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects.  Several of these buffers are never dealloced.  Some of them can be deallocated right after GSP-RM is initialized, but the rest need to stay until the driver unloads. Also futher bullet-proof these objects by poisoning the buffer and clearing the nvkm_gsp_mem object when it is deallocated.  Poisoning the buffer should trigger an error (or crash) from GSP-RM if it tries to access the buffer after we&amp;#39;ve deallocated it, because we were wrong about when it is safe to deallocate. Finally, change the mem-&amp;gt;size field to a size_t because that&amp;#39;s the same type that dma_alloc_coherent expects.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 56 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix several DMA buffer leaks Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects.  Several of these buffers are never dealloced.  Some of them can be deallocated right after GSP-RM is initialized, but the rest need to stay until the driver unloads. Also futher bullet-proof these objects by poisoning the buffer and clearing the nvkm_gsp_mem object when it is deallocated.  Poisoning the buffer should trigger an error (or crash) from GSP-RM if it tries to access the buffer after we&amp;#39;ve deallocated it, because we were wrong about when it is safe to deallocate. Finally, change the mem-&amp;gt;size field to a size_t because that&amp;#39;s the same type that dma_alloc_coherent expects.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26912</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0920 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0920</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0920</guid>
    </item>
  </channel>
</rss>
