<?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, 02 Oct 2026 18:43:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01509</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-01509</link>
      <description>bdu:2026-01509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-01509</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0509 — 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-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>EUVD-2026-344793</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344793</link>
      <description>EUVD-2026-344793</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344793</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49834</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49834</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: fix use-after-free bug of ns_writer on remount&lt;/p&gt;
&lt;p&gt;If a nilfs2 filesystem is downgraded to read-only due to metadata
corruption on disk and is remounted read/write, or if emergency read-only
remount is performed, detaching a log writer and synchronizing the
filesystem can be done at the same time.&lt;/p&gt;
&lt;p&gt;In these cases, use-after-free of the log writer (hereinafter
nilfs-&amp;gt;ns_writer) can happen as shown in the scenario below:&lt;/p&gt;
&lt;p&gt;Task1                               Task2
 --------------------------------    ------------------------------
 nilfs_construct_segment
   nilfs_segctor_sync
     init_wait
     init_waitqueue_entry
     add_wait_queue
     schedule
                                     nilfs_remount (R/W remount case)
				       nilfs_attach_log_writer
                                         nilfs_detach_log_writer
                                           nilfs_segctor_destroy
                                             kfree
     finish_wait
       _raw_spin_lock_irqsave
         __raw_spin_lock_irqsave
           do_raw_spin_lock
             debug_spin_lock_before  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;While Task1 is sleeping, nilfs-&amp;gt;ns_writer is freed by Task2.  After Task1
waked up, Task1 accesses nilfs-&amp;gt;ns_writer which is already freed.  This
scenario diagram is based on the Shigeru Yoshida&amp;#39;s post [1].&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not detaching nilfs-&amp;gt;ns_writer on remount so
that this UAF race doesn&amp;#39;t happen.…&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;nilfs2: fix use-after-free bug of ns_writer on remount&lt;/p&gt;
&lt;p&gt;If a nilfs2 filesystem is downgraded to read-only due to metadata
corruption on disk and is remounted read/write, or if emergency read-only
remount is performed, detaching a log writer and synchronizing the
filesystem can be done at the same time.&lt;/p&gt;
&lt;p&gt;In these cases, use-after-free of the log writer (hereinafter
nilfs-&amp;gt;ns_writer) can happen as shown in the scenario below:&lt;/p&gt;
&lt;p&gt;Task1                               Task2
 --------------------------------    ------------------------------
 nilfs_construct_segment
   nilfs_segctor_sync
     init_wait
     init_waitqueue_entry
     add_wait_queue
     schedule
                                     nilfs_remount (R/W remount case)
				       nilfs_attach_log_writer
                                         nilfs_detach_log_writer
                                           nilfs_segctor_destroy
                                             kfree
     finish_wait
       _raw_spin_lock_irqsave
         __raw_spin_lock_irqsave
           do_raw_spin_lock
             debug_spin_lock_before  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;While Task1 is sleeping, nilfs-&amp;gt;ns_writer is freed by Task2.  After Task1
waked up, Task1 accesses nilfs-&amp;gt;ns_writer which is already freed.  This
scenario diagram is based on the Shigeru Yoshida&amp;#39;s post [1].&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not detaching nilfs-&amp;gt;ns_writer on remount so
that this UAF race doesn&amp;#39;t happen.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49834</guid>
    </item>
    <item>
      <title>GHSA-7jwj-6g7w-4c9q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7jwj-6g7w-4c9q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: fix use-after-free bug of ns_writer on remount&lt;/p&gt;
&lt;p&gt;If a nilfs2 filesystem is downgraded to read-only due to metadata
corruption on disk and is remounted read/write, or if emergency read-only
remount is performed, detaching a log writer and synchronizing the
filesystem can be done at the same time.&lt;/p&gt;
&lt;p&gt;In these cases, use-after-free of the log writer (hereinafter
nilfs-&amp;gt;ns_writer) can happen as shown in the scenario below:&lt;/p&gt;
&lt;p&gt;Task1                               Task2
 --------------------------------    ------------------------------
 nilfs_construct_segment
   nilfs_segctor_sync
     init_wait
     init_waitqueue_entry
     add_wait_queue
     schedule
                                     nilfs_remount (R/W remount case)
				       nilfs_attach_log_writer
                                         nilfs_detach_log_writer
                                           nilfs_segctor_destroy
                                             kfree
     finish_wait
       _raw_spin_lock_irqsave
         __raw_spin_lock_irqsave
           do_raw_spin_lock
             debug_spin_lock_before  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;While Task1 is sleeping, nilfs-&amp;gt;ns_writer is freed by Task2.  After Task1
waked up, Task1 accesses nilfs-&amp;gt;ns_writer which is already freed.  This
scenario diagram is based on the Shigeru Yoshida&amp;#39;s post [1].&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not detaching nilfs-&amp;gt;ns_writer on remount so
that this UAF race doesn&amp;#39;t happen.…&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;nilfs2: fix use-after-free bug of ns_writer on remount&lt;/p&gt;
&lt;p&gt;If a nilfs2 filesystem is downgraded to read-only due to metadata
corruption on disk and is remounted read/write, or if emergency read-only
remount is performed, detaching a log writer and synchronizing the
filesystem can be done at the same time.&lt;/p&gt;
&lt;p&gt;In these cases, use-after-free of the log writer (hereinafter
nilfs-&amp;gt;ns_writer) can happen as shown in the scenario below:&lt;/p&gt;
&lt;p&gt;Task1                               Task2
 --------------------------------    ------------------------------
 nilfs_construct_segment
   nilfs_segctor_sync
     init_wait
     init_waitqueue_entry
     add_wait_queue
     schedule
                                     nilfs_remount (R/W remount case)
				       nilfs_attach_log_writer
                                         nilfs_detach_log_writer
                                           nilfs_segctor_destroy
                                             kfree
     finish_wait
       _raw_spin_lock_irqsave
         __raw_spin_lock_irqsave
           do_raw_spin_lock
             debug_spin_lock_before  &amp;lt;-- use-after-free&lt;/p&gt;
&lt;p&gt;While Task1 is sleeping, nilfs-&amp;gt;ns_writer is freed by Task2.  After Task1
waked up, Task1 accesses nilfs-&amp;gt;ns_writer which is already freed.  This
scenario diagram is based on the Shigeru Yoshida&amp;#39;s post [1].&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not detaching nilfs-&amp;gt;ns_writer on remount so
that this UAF race doesn&amp;#39;t happen.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7jwj-6g7w-4c9q</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-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:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49834</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49834</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: nilfs2: fix use-after-free bug of ns_writer on remount If a nilfs2 filesystem is downgraded to read-only due to metadata corruption on disk and is remounted read/write, or if emergency read-only remount is performed, detaching a log writer and synchronizing the filesystem can be done at the same time. In these cases, use-after-free of the log writer (hereinafter nilfs-&amp;gt;ns_writer) can happen as shown in the scenario below:  Task1                               Task2  --------------------------------    ------------------------------  nilfs_construct_segment    nilfs_segctor_sync      init_wait      init_waitqueue_entry      add_wait_queue      schedule                                      nilfs_remount (R/W remount case) 				       nilfs_attach_log_writer                                          nilfs_detach_log_writer                                            nilfs_segctor_destroy                                              kfree      finish_wait        _raw_spin_lock_irqsave          __raw_spin_lock_irqsave            do_raw_spin_lock              debug_spin_lock_before  &amp;lt;-- use-after-free While Task1 is sleeping, nilfs-&amp;gt;ns_writer is freed by Task2.  After Task1 waked up, Task1 accesses nilfs-&amp;gt;ns_writer which is already freed.  This scenario diagram is based on the Shigeru Yoshida&amp;#39;s post [1]. This patch fixes the issue by not detaching nilfs-&amp;gt;ns_writer on remount so that this UAF race doesn&amp;#39;t happen.  Alon…&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: nilfs2: fix use-after-free bug of ns_writer on remount If a nilfs2 filesystem is downgraded to read-only due to metadata corruption on disk and is remounted read/write, or if emergency read-only remount is performed, detaching a log writer and synchronizing the filesystem can be done at the same time. In these cases, use-after-free of the log writer (hereinafter nilfs-&amp;gt;ns_writer) can happen as shown in the scenario below:  Task1                               Task2  --------------------------------    ------------------------------  nilfs_construct_segment    nilfs_segctor_sync      init_wait      init_waitqueue_entry      add_wait_queue      schedule                                      nilfs_remount (R/W remount case) 				       nilfs_attach_log_writer                                          nilfs_detach_log_writer                                            nilfs_segctor_destroy                                              kfree      finish_wait        _raw_spin_lock_irqsave          __raw_spin_lock_irqsave            do_raw_spin_lock              debug_spin_lock_before  &amp;lt;-- use-after-free While Task1 is sleeping, nilfs-&amp;gt;ns_writer is freed by Task2.  After Task1 waked up, Task1 accesses nilfs-&amp;gt;ns_writer which is already freed.  This scenario diagram is based on the Shigeru Yoshida&amp;#39;s post [1]. This patch fixes the issue by not detaching nilfs-&amp;gt;ns_writer on remount so that this UAF race doesn&amp;#39;t happen.  Alon…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49834</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0922 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922</guid>
    </item>
  </channel>
</rss>
