<?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>Fri, 09 Oct 2026 12:53:48 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01559</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-01559</link>
      <description>bdu:2026-01559</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-01559</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38596</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38596</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38596</guid>
    </item>
    <item>
      <title>EUVD-2026-347118</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347118</link>
      <description>EUVD-2026-347118</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347118</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38596</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38596</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code&lt;/p&gt;
&lt;p&gt;The object is potentially already gone after the drm_gem_object_put().
In general the object should be fully constructed before calling
drm_gem_handle_create(), except the debugfs tracking uses a separate
lock and list and separate flag to denotate whether the object is
actually initialized.&lt;/p&gt;
&lt;p&gt;Since I&amp;#39;m touching this all anyway simplify this by only adding the
object to the debugfs when it&amp;#39;s ready for that, which allows us to
delete that separate flag. panthor_gem_debugfs_bo_rm() already checks
whether we&amp;#39;ve actually been added to the list or this is some error
path cleanup.&lt;/p&gt;
&lt;p&gt;v2: Fix build issues for !CONFIG_DEBUGFS (Adrián)&lt;/p&gt;
&lt;p&gt;v3: Add linebreak and remove outdated comment (Liviu)&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/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code&lt;/p&gt;
&lt;p&gt;The object is potentially already gone after the drm_gem_object_put().
In general the object should be fully constructed before calling
drm_gem_handle_create(), except the debugfs tracking uses a separate
lock and list and separate flag to denotate whether the object is
actually initialized.&lt;/p&gt;
&lt;p&gt;Since I&amp;#39;m touching this all anyway simplify this by only adding the
object to the debugfs when it&amp;#39;s ready for that, which allows us to
delete that separate flag. panthor_gem_debugfs_bo_rm() already checks
whether we&amp;#39;ve actually been added to the list or this is some error
path cleanup.&lt;/p&gt;
&lt;p&gt;v2: Fix build issues for !CONFIG_DEBUGFS (Adrián)&lt;/p&gt;
&lt;p&gt;v3: Add linebreak and remove outdated comment (Liviu)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38596</guid>
    </item>
    <item>
      <title>GHSA-c5gg-23m2-rg93</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c5gg-23m2-rg93</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code&lt;/p&gt;
&lt;p&gt;The object is potentially already gone after the drm_gem_object_put().
In general the object should be fully constructed before calling
drm_gem_handle_create(), except the debugfs tracking uses a separate
lock and list and separate flag to denotate whether the object is
actually initialized.&lt;/p&gt;
&lt;p&gt;Since I&amp;#39;m touching this all anyway simplify this by only adding the
object to the debugfs when it&amp;#39;s ready for that, which allows us to
delete that separate flag. panthor_gem_debugfs_bo_rm() already checks
whether we&amp;#39;ve actually been added to the list or this is some error
path cleanup.&lt;/p&gt;
&lt;p&gt;v2: Fix build issues for !CONFIG_DEBUGFS (Adrián)&lt;/p&gt;
&lt;p&gt;v3: Add linebreak and remove outdated comment (Liviu)&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/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code&lt;/p&gt;
&lt;p&gt;The object is potentially already gone after the drm_gem_object_put().
In general the object should be fully constructed before calling
drm_gem_handle_create(), except the debugfs tracking uses a separate
lock and list and separate flag to denotate whether the object is
actually initialized.&lt;/p&gt;
&lt;p&gt;Since I&amp;#39;m touching this all anyway simplify this by only adding the
object to the debugfs when it&amp;#39;s ready for that, which allows us to
delete that separate flag. panthor_gem_debugfs_bo_rm() already checks
whether we&amp;#39;ve actually been added to the list or this is some error
path cleanup.&lt;/p&gt;
&lt;p&gt;v2: Fix build issues for !CONFIG_DEBUGFS (Adrián)&lt;/p&gt;
&lt;p&gt;v3: Add linebreak and remove outdated comment (Liviu)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c5gg-23m2-rg93</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38596</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38596</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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code The object is potentially already gone after the drm_gem_object_put(). In general the object should be fully constructed before calling drm_gem_handle_create(), except the debugfs tracking uses a separate lock and list and separate flag to denotate whether the object is actually initialized. Since I&amp;#39;m touching this all anyway simplify this by only adding the object to the debugfs when it&amp;#39;s ready for that, which allows us to delete that separate flag. panthor_gem_debugfs_bo_rm() already checks whether we&amp;#39;ve actually been added to the list or this is some error path cleanup. v2: Fix build issues for !CONFIG_DEBUGFS (Adrián) v3: Add linebreak and remove outdated comment (Liviu)&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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code The object is potentially already gone after the drm_gem_object_put(). In general the object should be fully constructed before calling drm_gem_handle_create(), except the debugfs tracking uses a separate lock and list and separate flag to denotate whether the object is actually initialized. Since I&amp;#39;m touching this all anyway simplify this by only adding the object to the debugfs when it&amp;#39;s ready for that, which allows us to delete that separate flag. panthor_gem_debugfs_bo_rm() already checks whether we&amp;#39;ve actually been added to the list or this is some error path cleanup. v2: Fix build issues for !CONFIG_DEBUGFS (Adrián) v3: Add linebreak and remove outdated comment (Liviu)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38596</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1869 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1869</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1869</guid>
    </item>
  </channel>
</rss>
