<?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>Sun, 04 Oct 2026 14:49:59 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-01858</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-01858</link>
      <description>bdu:2024-01858</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-01858</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-52449</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-52449</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-52449</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0226 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux d'Ubuntu&lt;/span&gt;. Certaines d'e…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0226</link>
      <description>certfr-2024-avi-0226</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0226</guid>
    </item>
    <item>
      <title>EUVD-2026-311512</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311512</link>
      <description>EUVD-2026-311512</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311512</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52449</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-52449</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mtd: Fix gluebi NULL pointer dereference caused by ftl notifier&lt;/p&gt;
&lt;p&gt;If both ftl.ko and gluebi.ko are loaded, the notifier of ftl
triggers NULL pointer dereference when trying to access
‘gluebi-&amp;gt;desc’ in gluebi_read().&lt;/p&gt;
&lt;p&gt;ubi_gluebi_init
  ubi_register_volume_notifier
    ubi_enumerate_volumes
      ubi_notify_all
        gluebi_notify    nb-&amp;gt;notifier_call()
          gluebi_create
            mtd_device_register
              mtd_device_parse_register
                add_mtd_device
                  blktrans_notify_add   not-&amp;gt;add()
                    ftl_add_mtd         tr-&amp;gt;add_mtd()
                      scan_header
                        mtd_read
                          mtd_read_oob
                            mtd_read_oob_std
                              gluebi_read   mtd-&amp;gt;read()
                                gluebi-&amp;gt;desc - NULL&lt;/p&gt;
&lt;p&gt;Detailed reproduction information available at the Link [1],&lt;/p&gt;
&lt;p&gt;In the normal case, obtain gluebi-&amp;gt;desc in the gluebi_get_device(),
and access gluebi-&amp;gt;desc in the gluebi_read(). However,
gluebi_get_device() is not executed in advance in the
ftl_add_mtd() process, which leads to NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;The solution for the gluebi module is to run jffs2 on the UBI
volume without considering working with ftl or mtdblock [2].
Therefore, this problem can be avoided by preventing gluebi from
creating the mtdblock device after creating mtd partition of the
type MTD_UBIVOLUME.&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;mtd: Fix gluebi NULL pointer dereference caused by ftl notifier&lt;/p&gt;
&lt;p&gt;If both ftl.ko and gluebi.ko are loaded, the notifier of ftl
triggers NULL pointer dereference when trying to access
‘gluebi-&amp;gt;desc’ in gluebi_read().&lt;/p&gt;
&lt;p&gt;ubi_gluebi_init
  ubi_register_volume_notifier
    ubi_enumerate_volumes
      ubi_notify_all
        gluebi_notify    nb-&amp;gt;notifier_call()
          gluebi_create
            mtd_device_register
              mtd_device_parse_register
                add_mtd_device
                  blktrans_notify_add   not-&amp;gt;add()
                    ftl_add_mtd         tr-&amp;gt;add_mtd()
                      scan_header
                        mtd_read
                          mtd_read_oob
                            mtd_read_oob_std
                              gluebi_read   mtd-&amp;gt;read()
                                gluebi-&amp;gt;desc - NULL&lt;/p&gt;
&lt;p&gt;Detailed reproduction information available at the Link [1],&lt;/p&gt;
&lt;p&gt;In the normal case, obtain gluebi-&amp;gt;desc in the gluebi_get_device(),
and access gluebi-&amp;gt;desc in the gluebi_read(). However,
gluebi_get_device() is not executed in advance in the
ftl_add_mtd() process, which leads to NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;The solution for the gluebi module is to run jffs2 on the UBI
volume without considering working with ftl or mtdblock [2].
Therefore, this problem can be avoided by preventing gluebi from
creating the mtdblock device after creating mtd partition of the
type MTD_UBIVOLUME.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-52449</guid>
    </item>
    <item>
      <title>GHSA-268r-8rwm-mqq9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-268r-8rwm-mqq9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mtd: Fix gluebi NULL pointer dereference caused by ftl notifier&lt;/p&gt;
&lt;p&gt;If both ftl.ko and gluebi.ko are loaded, the notifier of ftl
triggers NULL pointer dereference when trying to access
‘gluebi-&amp;gt;desc’ in gluebi_read().&lt;/p&gt;
&lt;p&gt;ubi_gluebi_init
  ubi_register_volume_notifier
    ubi_enumerate_volumes
      ubi_notify_all
        gluebi_notify    nb-&amp;gt;notifier_call()
          gluebi_create
            mtd_device_register
              mtd_device_parse_register
                add_mtd_device
                  blktrans_notify_add   not-&amp;gt;add()
                    ftl_add_mtd         tr-&amp;gt;add_mtd()
                      scan_header
                        mtd_read
                          mtd_read_oob
                            mtd_read_oob_std
                              gluebi_read   mtd-&amp;gt;read()
                                gluebi-&amp;gt;desc - NULL&lt;/p&gt;
&lt;p&gt;Detailed reproduction information available at the Link [1],&lt;/p&gt;
&lt;p&gt;In the normal case, obtain gluebi-&amp;gt;desc in the gluebi_get_device(),
and access gluebi-&amp;gt;desc in the gluebi_read(). However,
gluebi_get_device() is not executed in advance in the
ftl_add_mtd() process, which leads to NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;The solution for the gluebi module is to run jffs2 on the UBI
volume without considering working with ftl or mtdblock [2].
Therefore, this problem can be avoided by preventing gluebi from
creating the mtdblock device after creating mtd partition of the
type MTD_UBIVOLUME.&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;mtd: Fix gluebi NULL pointer dereference caused by ftl notifier&lt;/p&gt;
&lt;p&gt;If both ftl.ko and gluebi.ko are loaded, the notifier of ftl
triggers NULL pointer dereference when trying to access
‘gluebi-&amp;gt;desc’ in gluebi_read().&lt;/p&gt;
&lt;p&gt;ubi_gluebi_init
  ubi_register_volume_notifier
    ubi_enumerate_volumes
      ubi_notify_all
        gluebi_notify    nb-&amp;gt;notifier_call()
          gluebi_create
            mtd_device_register
              mtd_device_parse_register
                add_mtd_device
                  blktrans_notify_add   not-&amp;gt;add()
                    ftl_add_mtd         tr-&amp;gt;add_mtd()
                      scan_header
                        mtd_read
                          mtd_read_oob
                            mtd_read_oob_std
                              gluebi_read   mtd-&amp;gt;read()
                                gluebi-&amp;gt;desc - NULL&lt;/p&gt;
&lt;p&gt;Detailed reproduction information available at the Link [1],&lt;/p&gt;
&lt;p&gt;In the normal case, obtain gluebi-&amp;gt;desc in the gluebi_get_device(),
and access gluebi-&amp;gt;desc in the gluebi_read(). However,
gluebi_get_device() is not executed in advance in the
ftl_add_mtd() process, which leads to NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;The solution for the gluebi module is to run jffs2 on the UBI
volume without considering working with ftl or mtdblock [2].
Therefore, this problem can be avoided by preventing gluebi from
creating the mtdblock device after creating mtd partition of the
type MTD_UBIVOLUME.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-268r-8rwm-mqq9</guid>
    </item>
    <item>
      <title>gsd-2023-52449</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-52449</link>
      <description>gsd-2023-52449</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-52449</guid>
    </item>
    <item>
      <title>OESA-2024-1296 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1296</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: pvrusb2: fix use after free on context disconnection&#13;
&#13;
Upon module load, a kthread is created targeting the
pvr2_context_thread_func function, which may call pvr2_context_destroy
and thus call kfree() on the context object. However, that might happen
before the usb hub_event handler is able to notify the driver. This
patch adds a sanity check before the invalid read reported by syzbot,
within the context disconnection call stack.(CVE-2023-52445)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
mtd: Fix gluebi NULL pointer dereference caused by ftl notifier&#13;
&#13;
If both ftl.ko and gluebi.ko are loaded, the notifier of ftl
triggers NULL pointer dereference when trying to access
‘gluebi-&amp;amp;gt;desc’ in gluebi_read().&#13;
&#13;
ubi_gluebi_init
  ubi_register_volume_notifier
    ubi_enumerate_volumes
      ubi_notify_all
        gluebi_notify    nb-&amp;amp;gt;notifier_call()
          gluebi_create
            mtd_device_register
              mtd_device_parse_register
                add_mtd_device
                  blktrans_notify_add   not-&amp;amp;gt;add()
                    ftl_add_mtd         tr-&amp;amp;gt;add_mtd()
                      scan_header
                        mtd_read
                          mtd_read_oob
                            mtd_read_oob_std
                              gluebi_read   mtd-&amp;amp;gt;read()…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
media: pvrusb2: fix use after free on context disconnection&#13;
&#13;
Upon module load, a kthread is created targeting the
pvr2_context_thread_func function, which may call pvr2_context_destroy
and thus call kfree() on the context object. However, that might happen
before the usb hub_event handler is able to notify the driver. This
patch adds a sanity check before the invalid read reported by syzbot,
within the context disconnection call stack.(CVE-2023-52445)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
mtd: Fix gluebi NULL pointer dereference caused by ftl notifier&#13;
&#13;
If both ftl.ko and gluebi.ko are loaded, the notifier of ftl
triggers NULL pointer dereference when trying to access
‘gluebi-&amp;amp;gt;desc’ in gluebi_read().&#13;
&#13;
ubi_gluebi_init
  ubi_register_volume_notifier
    ubi_enumerate_volumes
      ubi_notify_all
        gluebi_notify    nb-&amp;amp;gt;notifier_call()
          gluebi_create
            mtd_device_register
              mtd_device_parse_register
                add_mtd_device
                  blktrans_notify_add   not-&amp;amp;gt;add()
                    ftl_add_mtd         tr-&amp;amp;gt;add_mtd()
                      scan_header
                        mtd_read
                          mtd_read_oob
                            mtd_read_oob_std
                              gluebi_read   mtd-&amp;amp;gt;read()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1296</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:0855-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:0855-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-2024:0855-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52449</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52449</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mtd: Fix gluebi NULL pointer dereference caused by ftl notifier If both ftl.ko and gluebi.ko are loaded, the notifier of ftl triggers NULL pointer dereference when trying to access ‘gluebi-&amp;gt;desc’ in gluebi_read(). ubi_gluebi_init   ubi_register_volume_notifier     ubi_enumerate_volumes       ubi_notify_all         gluebi_notify    nb-&amp;gt;notifier_call()           gluebi_create             mtd_device_register               mtd_device_parse_register                 add_mtd_device                   blktrans_notify_add   not-&amp;gt;add()                     ftl_add_mtd         tr-&amp;gt;add_mtd()                       scan_header                         mtd_read                           mtd_read_oob                             mtd_read_oob_std                               gluebi_read   mtd-&amp;gt;read()                                 gluebi-&amp;gt;desc - NULL Detailed reproduction information available at the Link [1], In the normal case, obtain gluebi-&amp;gt;desc in the gluebi_get_device(), and access gluebi-&amp;gt;desc in the gluebi_read(). However, gluebi_get_device() is not executed in advance in the ftl_add_mtd() process, which leads to NULL pointer dereference. The solution for the gluebi module is to run jffs2 on the UBI volume without considering working with ftl or mtdblock [2]. Therefore, this problem can be avoided by preventing gluebi from creating the mtdblock device after creating mtd partition of the type MTD_UBIVOLUME.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mtd: Fix gluebi NULL pointer dereference caused by ftl notifier If both ftl.ko and gluebi.ko are loaded, the notifier of ftl triggers NULL pointer dereference when trying to access ‘gluebi-&amp;gt;desc’ in gluebi_read(). ubi_gluebi_init   ubi_register_volume_notifier     ubi_enumerate_volumes       ubi_notify_all         gluebi_notify    nb-&amp;gt;notifier_call()           gluebi_create             mtd_device_register               mtd_device_parse_register                 add_mtd_device                   blktrans_notify_add   not-&amp;gt;add()                     ftl_add_mtd         tr-&amp;gt;add_mtd()                       scan_header                         mtd_read                           mtd_read_oob                             mtd_read_oob_std                               gluebi_read   mtd-&amp;gt;read()                                 gluebi-&amp;gt;desc - NULL Detailed reproduction information available at the Link [1], In the normal case, obtain gluebi-&amp;gt;desc in the gluebi_get_device(), and access gluebi-&amp;gt;desc in the gluebi_read(). However, gluebi_get_device() is not executed in advance in the ftl_add_mtd() process, which leads to NULL pointer dereference. The solution for the gluebi module is to run jffs2 on the UBI volume without considering working with ftl or mtdblock [2]. Therefore, this problem can be avoided by preventing gluebi from creating the mtdblock device after creating mtd partition of the type MTD_UBIVOLUME.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52449</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0473 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0473</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-0473</guid>
    </item>
  </channel>
</rss>
