<?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>Sat, 03 Oct 2026 22:12:33 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12904</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12904</link>
      <description>bdu:2025-12904</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12904</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53514</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53514</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-2023-53514</guid>
    </item>
    <item>
      <title>EUVD-2026-312103</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312103</link>
      <description>EUVD-2026-312103</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312103</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53514</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53514</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gpu: host1x: Fix memory leak of device names&lt;/p&gt;
&lt;p&gt;The device names allocated by dev_set_name() need be freed
before module unloading, but they can not be freed because
the kobject&amp;#39;s refcount which was set in device_initialize()
has not be decreased to 0.&lt;/p&gt;
&lt;p&gt;As comment of device_add() says, if it fails, use only
put_device() drop the refcount, then the name will be
freed in kobejct_cleanup().&lt;/p&gt;
&lt;p&gt;device_del() and put_device() can be replaced with
device_unregister(), so call it to unregister the added
successfully devices, and just call put_device() to the
not added device.&lt;/p&gt;
&lt;p&gt;Add a release() function to device to avoid null release()
function WARNING in device_release(), it&amp;#39;s empty, because
the context devices are freed together in
host1x_memory_context_list_free().&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;gpu: host1x: Fix memory leak of device names&lt;/p&gt;
&lt;p&gt;The device names allocated by dev_set_name() need be freed
before module unloading, but they can not be freed because
the kobject&amp;#39;s refcount which was set in device_initialize()
has not be decreased to 0.&lt;/p&gt;
&lt;p&gt;As comment of device_add() says, if it fails, use only
put_device() drop the refcount, then the name will be
freed in kobejct_cleanup().&lt;/p&gt;
&lt;p&gt;device_del() and put_device() can be replaced with
device_unregister(), so call it to unregister the added
successfully devices, and just call put_device() to the
not added device.&lt;/p&gt;
&lt;p&gt;Add a release() function to device to avoid null release()
function WARNING in device_release(), it&amp;#39;s empty, because
the context devices are freed together in
host1x_memory_context_list_free().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53514</guid>
    </item>
    <item>
      <title>GHSA-8gw4-3w27-23g9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8gw4-3w27-23g9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gpu: host1x: Fix memory leak of device names&lt;/p&gt;
&lt;p&gt;The device names allocated by dev_set_name() need be freed
before module unloading, but they can not be freed because
the kobject&amp;#39;s refcount which was set in device_initialize()
has not be decreased to 0.&lt;/p&gt;
&lt;p&gt;As comment of device_add() says, if it fails, use only
put_device() drop the refcount, then the name will be
freed in kobejct_cleanup().&lt;/p&gt;
&lt;p&gt;device_del() and put_device() can be replaced with
device_unregister(), so call it to unregister the added
successfully devices, and just call put_device() to the
not added device.&lt;/p&gt;
&lt;p&gt;Add a release() function to device to avoid null release()
function WARNING in device_release(), it&amp;#39;s empty, because
the context devices are freed together in
host1x_memory_context_list_free().&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;gpu: host1x: Fix memory leak of device names&lt;/p&gt;
&lt;p&gt;The device names allocated by dev_set_name() need be freed
before module unloading, but they can not be freed because
the kobject&amp;#39;s refcount which was set in device_initialize()
has not be decreased to 0.&lt;/p&gt;
&lt;p&gt;As comment of device_add() says, if it fails, use only
put_device() drop the refcount, then the name will be
freed in kobejct_cleanup().&lt;/p&gt;
&lt;p&gt;device_del() and put_device() can be replaced with
device_unregister(), so call it to unregister the added
successfully devices, and just call put_device() to the
not added device.&lt;/p&gt;
&lt;p&gt;Add a release() function to device to avoid null release()
function WARNING in device_release(), it&amp;#39;s empty, because
the context devices are freed together in
host1x_memory_context_list_free().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8gw4-3w27-23g9</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53514</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53514</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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Fix memory leak of device names The device names allocated by dev_set_name() need be freed before module unloading, but they can not be freed because the kobject&amp;#39;s refcount which was set in device_initialize() has not be decreased to 0. As comment of device_add() says, if it fails, use only put_device() drop the refcount, then the name will be freed in kobejct_cleanup(). device_del() and put_device() can be replaced with device_unregister(), so call it to unregister the added successfully devices, and just call put_device() to the not added device. Add a release() function to device to avoid null release() function WARNING in device_release(), it&amp;#39;s empty, because the context devices are freed together in host1x_memory_context_list_free().&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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Fix memory leak of device names The device names allocated by dev_set_name() need be freed before module unloading, but they can not be freed because the kobject&amp;#39;s refcount which was set in device_initialize() has not be decreased to 0. As comment of device_add() says, if it fails, use only put_device() drop the refcount, then the name will be freed in kobejct_cleanup(). device_del() and put_device() can be replaced with device_unregister(), so call it to unregister the added successfully devices, and just call put_device() to the not added device. Add a release() function to device to avoid null release() function WARNING in device_release(), it&amp;#39;s empty, because the context devices are freed together in host1x_memory_context_list_free().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53514</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</guid>
    </item>
  </channel>
</rss>
