<?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 21:53:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03719</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03719</link>
      <description>bdu:2026-03719</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03719</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0607 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0607</link>
      <description>certfr-2025-avi-0607</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0607</guid>
    </item>
    <item>
      <title>EUVD-2026-310801</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310801</link>
      <description>EUVD-2026-310801</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310801</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49780</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49780</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()&lt;/p&gt;
&lt;p&gt;If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated
by dev_set_name() need be freed. As comment of device_register() says, it
should use put_device() to give up the reference in the error path. So fix
this by calling put_device(), then the name can be freed in kobject_cleanup().
The &amp;#39;tl_hba&amp;#39; will be freed in tcm_loop_release_adapter(), so it don&amp;#39;t need
goto error label in this case.&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;scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()&lt;/p&gt;
&lt;p&gt;If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated
by dev_set_name() need be freed. As comment of device_register() says, it
should use put_device() to give up the reference in the error path. So fix
this by calling put_device(), then the name can be freed in kobject_cleanup().
The &amp;#39;tl_hba&amp;#39; will be freed in tcm_loop_release_adapter(), so it don&amp;#39;t need
goto error label in this case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49780</guid>
    </item>
    <item>
      <title>GHSA-px2q-r9rv-q5m3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-px2q-r9rv-q5m3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()&lt;/p&gt;
&lt;p&gt;If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated
by dev_set_name() need be freed. As comment of device_register() says, it
should use put_device() to give up the reference in the error path. So fix
this by calling put_device(), then the name can be freed in kobject_cleanup().
The &amp;#39;tl_hba&amp;#39; will be freed in tcm_loop_release_adapter(), so it don&amp;#39;t need
goto error label in this case.&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;scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()&lt;/p&gt;
&lt;p&gt;If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated
by dev_set_name() need be freed. As comment of device_register() says, it
should use put_device() to give up the reference in the error path. So fix
this by calling put_device(), then the name can be freed in kobject_cleanup().
The &amp;#39;tl_hba&amp;#39; will be freed in tcm_loop_release_adapter(), so it don&amp;#39;t need
goto error label in this case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-px2q-r9rv-q5m3</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02334-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02334-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:02334-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49780</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49780</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus() If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(). The &amp;#39;tl_hba&amp;#39; will be freed in tcm_loop_release_adapter(), so it don&amp;#39;t need goto error label in this case.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus() If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(). The &amp;#39;tl_hba&amp;#39; will be freed in tcm_loop_release_adapter(), so it don&amp;#39;t need goto error label in this case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49780</guid>
    </item>
  </channel>
</rss>
