<?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 20:46:33 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06636</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06636</link>
      <description>bdu:2024-06636</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06636</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0779 — 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-2024-avi-0779</link>
      <description>certfr-2024-avi-0779</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779</guid>
    </item>
    <item>
      <title>EUVD-2026-310247</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310247</link>
      <description>EUVD-2026-310247</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310247</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48931</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48931</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;configfs: fix a race in configfs_{,un}register_subsystem()&lt;/p&gt;
&lt;p&gt;When configfs_register_subsystem() or configfs_unregister_subsystem()
is executing link_group() or unlink_group(),
it is possible that two processes add or delete list concurrently.
Some unfortunate interleavings of them can cause kernel panic.&lt;/p&gt;
&lt;p&gt;One of cases is:
A --&amp;gt; B --&amp;gt; C --&amp;gt; D
A &amp;lt;-- B &amp;lt;-- C &amp;lt;-- D&lt;/p&gt;
&lt;p&gt;delete list_head *B        |      delete list_head *C
--------------------------------|-----------------------------------
configfs_unregister_subsystem   |   configfs_unregister_subsystem
  unlink_group                  |     unlink_group
    unlink_obj                  |       unlink_obj
      list_del_init             |         list_del_init
        __list_del_entry        |           __list_del_entry
          __list_del            |             __list_del
            // next == C        |
            next-&amp;gt;prev = prev   |
                                |               next-&amp;gt;prev = prev
            prev-&amp;gt;next = next   |
                                |                 // prev == B
                                |                 prev-&amp;gt;next = next&lt;/p&gt;
&lt;p&gt;Fix this by adding mutex when calling link_group() or unlink_group(),
but parent configfs_subsystem is NULL when config_item is root.
So I create a mutex configfs_subsystem_mutex.&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;configfs: fix a race in configfs_{,un}register_subsystem()&lt;/p&gt;
&lt;p&gt;When configfs_register_subsystem() or configfs_unregister_subsystem()
is executing link_group() or unlink_group(),
it is possible that two processes add or delete list concurrently.
Some unfortunate interleavings of them can cause kernel panic.&lt;/p&gt;
&lt;p&gt;One of cases is:
A --&amp;gt; B --&amp;gt; C --&amp;gt; D
A &amp;lt;-- B &amp;lt;-- C &amp;lt;-- D&lt;/p&gt;
&lt;p&gt;delete list_head *B        |      delete list_head *C
--------------------------------|-----------------------------------
configfs_unregister_subsystem   |   configfs_unregister_subsystem
  unlink_group                  |     unlink_group
    unlink_obj                  |       unlink_obj
      list_del_init             |         list_del_init
        __list_del_entry        |           __list_del_entry
          __list_del            |             __list_del
            // next == C        |
            next-&amp;gt;prev = prev   |
                                |               next-&amp;gt;prev = prev
            prev-&amp;gt;next = next   |
                                |                 // prev == B
                                |                 prev-&amp;gt;next = next&lt;/p&gt;
&lt;p&gt;Fix this by adding mutex when calling link_group() or unlink_group(),
but parent configfs_subsystem is NULL when config_item is root.
So I create a mutex configfs_subsystem_mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48931</guid>
    </item>
    <item>
      <title>GHSA-38qw-v9q4-hm9j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-38qw-v9q4-hm9j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;configfs: fix a race in configfs_{,un}register_subsystem()&lt;/p&gt;
&lt;p&gt;When configfs_register_subsystem() or configfs_unregister_subsystem()
is executing link_group() or unlink_group(),
it is possible that two processes add or delete list concurrently.
Some unfortunate interleavings of them can cause kernel panic.&lt;/p&gt;
&lt;p&gt;One of cases is:
A --&amp;gt; B --&amp;gt; C --&amp;gt; D
A &amp;lt;-- B &amp;lt;-- C &amp;lt;-- D&lt;/p&gt;
&lt;p&gt;delete list_head *B        |      delete list_head *C
--------------------------------|-----------------------------------
configfs_unregister_subsystem   |   configfs_unregister_subsystem
  unlink_group                  |     unlink_group
    unlink_obj                  |       unlink_obj
      list_del_init             |         list_del_init
        __list_del_entry        |           __list_del_entry
          __list_del            |             __list_del
            // next == C        |
            next-&amp;gt;prev = prev   |
                                |               next-&amp;gt;prev = prev
            prev-&amp;gt;next = next   |
                                |                 // prev == B
                                |                 prev-&amp;gt;next = next&lt;/p&gt;
&lt;p&gt;Fix this by adding mutex when calling link_group() or unlink_group(),
but parent configfs_subsystem is NULL when config_item is root.
So I create a mutex configfs_subsystem_mutex.&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;configfs: fix a race in configfs_{,un}register_subsystem()&lt;/p&gt;
&lt;p&gt;When configfs_register_subsystem() or configfs_unregister_subsystem()
is executing link_group() or unlink_group(),
it is possible that two processes add or delete list concurrently.
Some unfortunate interleavings of them can cause kernel panic.&lt;/p&gt;
&lt;p&gt;One of cases is:
A --&amp;gt; B --&amp;gt; C --&amp;gt; D
A &amp;lt;-- B &amp;lt;-- C &amp;lt;-- D&lt;/p&gt;
&lt;p&gt;delete list_head *B        |      delete list_head *C
--------------------------------|-----------------------------------
configfs_unregister_subsystem   |   configfs_unregister_subsystem
  unlink_group                  |     unlink_group
    unlink_obj                  |       unlink_obj
      list_del_init             |         list_del_init
        __list_del_entry        |           __list_del_entry
          __list_del            |             __list_del
            // next == C        |
            next-&amp;gt;prev = prev   |
                                |               next-&amp;gt;prev = prev
            prev-&amp;gt;next = next   |
                                |                 // prev == B
                                |                 prev-&amp;gt;next = next&lt;/p&gt;
&lt;p&gt;Fix this by adding mutex when calling link_group() or unlink_group(),
but parent configfs_subsystem is NULL when config_item is root.
So I create a mutex configfs_subsystem_mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-38qw-v9q4-hm9j</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3189-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3189-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:3189-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48931</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48931</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 121 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: configfs: fix a race in configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem() is executing link_group() or unlink_group(), it is possible that two processes add or delete list concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --&amp;gt; B --&amp;gt; C --&amp;gt; D A &amp;lt;-- B &amp;lt;-- C &amp;lt;-- D      delete list_head *B        |      delete list_head *C --------------------------------|----------------------------------- configfs_unregister_subsystem   |   configfs_unregister_subsystem   unlink_group                  |     unlink_group     unlink_obj                  |       unlink_obj       list_del_init             |         list_del_init         __list_del_entry        |           __list_del_entry           __list_del            |             __list_del             // next == C        |             next-&amp;gt;prev = prev   |                                 |               next-&amp;gt;prev = prev             prev-&amp;gt;next = next   |                                 |                 // prev == B                                 |                 prev-&amp;gt;next = next Fix this by adding mutex when calling link_group() or unlink_group(), but parent configfs_subsystem is NULL when config_item is root. So I create a mutex configfs_subsystem_mutex.&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 121 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: configfs: fix a race in configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem() is executing link_group() or unlink_group(), it is possible that two processes add or delete list concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --&amp;gt; B --&amp;gt; C --&amp;gt; D A &amp;lt;-- B &amp;lt;-- C &amp;lt;-- D      delete list_head *B        |      delete list_head *C --------------------------------|----------------------------------- configfs_unregister_subsystem   |   configfs_unregister_subsystem   unlink_group                  |     unlink_group     unlink_obj                  |       unlink_obj       list_del_init             |         list_del_init         __list_del_entry        |           __list_del_entry           __list_del            |             __list_del             // next == C        |             next-&amp;gt;prev = prev   |                                 |               next-&amp;gt;prev = prev             prev-&amp;gt;next = next   |                                 |                 // prev == B                                 |                 prev-&amp;gt;next = next Fix this by adding mutex when calling link_group() or unlink_group(), but parent configfs_subsystem is NULL when config_item is root. So I create a mutex configfs_subsystem_mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48931</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1898 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1898</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen 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 zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1898</guid>
    </item>
  </channel>
</rss>
