<?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 10:19:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-09392</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-09392</link>
      <description>bdu:2024-09392</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-09392</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0999 — 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-0999</link>
      <description>certfr-2024-avi-0999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999</guid>
    </item>
    <item>
      <title>EUVD-2026-320254</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320254</link>
      <description>EUVD-2026-320254</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320254</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48664</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48664</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix hang during unmount when stopping a space reclaim worker&lt;/p&gt;
&lt;p&gt;Often when running generic/562 from fstests we can hang during unmount,
resulting in a trace like this:&lt;/p&gt;
&lt;p&gt;Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00
  Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.
  Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1
  Sep 07 11:55:32 debian9 kernel: &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000
  Sep 07 11:55:32 debian9 kernel: Call Trace:
  Sep 07 11:55:32 debian9 kernel:  &amp;lt;TASK&amp;gt;
  Sep 07 11:55:32 debian9 kernel:  __schedule+0x3c8/0xec0
  Sep 07 11:55:32 debian9 kernel:  ? rcu_read_lock_sched_held+0x12/0x70
  Sep 07 11:55:32 debian9 kernel:  schedule+0x5d/0xf0
  Sep 07 11:55:32 debian9 kernel:  schedule_timeout+0xf1/0x130
  Sep 07 11:55:32 debian9 kernel:  ? lock_release+0x224/0x4a0
  Sep 07 11:55:32 debian9 kernel:  ? lock_acquired+0x1a0/0x420
  Sep 07 11:55:32 debian9 kernel:  ? trace_hardirqs_on+0x2c/0xd0
  Sep 07 11:55:32 debian9 kernel:  __wait_for_common+0xac/0x200
  Sep 07 11:55:32 debian9 kernel:  ? usleep_range_state+0xb0/0xb0
  Sep 07 11:55:32 debian9 kernel:  __flush_work+0x26d/0x530
  Sep 07 11:55:32 debian9 kernel:  ? flush_workqueue_prep_pwqs+0…&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;btrfs: fix hang during unmount when stopping a space reclaim worker&lt;/p&gt;
&lt;p&gt;Often when running generic/562 from fstests we can hang during unmount,
resulting in a trace like this:&lt;/p&gt;
&lt;p&gt;Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00
  Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.
  Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1
  Sep 07 11:55:32 debian9 kernel: &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000
  Sep 07 11:55:32 debian9 kernel: Call Trace:
  Sep 07 11:55:32 debian9 kernel:  &amp;lt;TASK&amp;gt;
  Sep 07 11:55:32 debian9 kernel:  __schedule+0x3c8/0xec0
  Sep 07 11:55:32 debian9 kernel:  ? rcu_read_lock_sched_held+0x12/0x70
  Sep 07 11:55:32 debian9 kernel:  schedule+0x5d/0xf0
  Sep 07 11:55:32 debian9 kernel:  schedule_timeout+0xf1/0x130
  Sep 07 11:55:32 debian9 kernel:  ? lock_release+0x224/0x4a0
  Sep 07 11:55:32 debian9 kernel:  ? lock_acquired+0x1a0/0x420
  Sep 07 11:55:32 debian9 kernel:  ? trace_hardirqs_on+0x2c/0xd0
  Sep 07 11:55:32 debian9 kernel:  __wait_for_common+0xac/0x200
  Sep 07 11:55:32 debian9 kernel:  ? usleep_range_state+0xb0/0xb0
  Sep 07 11:55:32 debian9 kernel:  __flush_work+0x26d/0x530
  Sep 07 11:55:32 debian9 kernel:  ? flush_workqueue_prep_pwqs+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48664</guid>
    </item>
    <item>
      <title>GHSA-w94g-q3rj-7p4m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w94g-q3rj-7p4m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix hang during unmount when stopping a space reclaim worker&lt;/p&gt;
&lt;p&gt;Often when running generic/562 from fstests we can hang during unmount,
resulting in a trace like this:&lt;/p&gt;
&lt;p&gt;Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00
  Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.
  Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1
  Sep 07 11:55:32 debian9 kernel: &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000
  Sep 07 11:55:32 debian9 kernel: Call Trace:
  Sep 07 11:55:32 debian9 kernel:  &amp;lt;TASK&amp;gt;
  Sep 07 11:55:32 debian9 kernel:  __schedule+0x3c8/0xec0
  Sep 07 11:55:32 debian9 kernel:  ? rcu_read_lock_sched_held+0x12/0x70
  Sep 07 11:55:32 debian9 kernel:  schedule+0x5d/0xf0
  Sep 07 11:55:32 debian9 kernel:  schedule_timeout+0xf1/0x130
  Sep 07 11:55:32 debian9 kernel:  ? lock_release+0x224/0x4a0
  Sep 07 11:55:32 debian9 kernel:  ? lock_acquired+0x1a0/0x420
  Sep 07 11:55:32 debian9 kernel:  ? trace_hardirqs_on+0x2c/0xd0
  Sep 07 11:55:32 debian9 kernel:  __wait_for_common+0xac/0x200
  Sep 07 11:55:32 debian9 kernel:  ? usleep_range_state+0xb0/0xb0
  Sep 07 11:55:32 debian9 kernel:  __flush_work+0x26d/0x530
  Sep 07 11:55:32 debian9 kernel:  ? flush_workqueue_prep_pwqs+0…&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;btrfs: fix hang during unmount when stopping a space reclaim worker&lt;/p&gt;
&lt;p&gt;Often when running generic/562 from fstests we can hang during unmount,
resulting in a trace like this:&lt;/p&gt;
&lt;p&gt;Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00
  Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.
  Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1
  Sep 07 11:55:32 debian9 kernel: &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000
  Sep 07 11:55:32 debian9 kernel: Call Trace:
  Sep 07 11:55:32 debian9 kernel:  &amp;lt;TASK&amp;gt;
  Sep 07 11:55:32 debian9 kernel:  __schedule+0x3c8/0xec0
  Sep 07 11:55:32 debian9 kernel:  ? rcu_read_lock_sched_held+0x12/0x70
  Sep 07 11:55:32 debian9 kernel:  schedule+0x5d/0xf0
  Sep 07 11:55:32 debian9 kernel:  schedule_timeout+0xf1/0x130
  Sep 07 11:55:32 debian9 kernel:  ? lock_release+0x224/0x4a0
  Sep 07 11:55:32 debian9 kernel:  ? lock_acquired+0x1a0/0x420
  Sep 07 11:55:32 debian9 kernel:  ? trace_hardirqs_on+0x2c/0xd0
  Sep 07 11:55:32 debian9 kernel:  __wait_for_common+0xac/0x200
  Sep 07 11:55:32 debian9 kernel:  ? usleep_range_state+0xb0/0xb0
  Sep 07 11:55:32 debian9 kernel:  __flush_work+0x26d/0x530
  Sep 07 11:55:32 debian9 kernel:  ? flush_workqueue_prep_pwqs+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w94g-q3rj-7p4m</guid>
    </item>
    <item>
      <title>gsd-2022-48664</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-48664</link>
      <description>gsd-2022-48664</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-48664</guid>
    </item>
    <item>
      <title>OESA-2024-1651 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1651</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;
s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup&#13;
&#13;
Fix Oops in dasd_alias_get_start_dev() function caused by the pavgroup
pointer being NULL.&#13;
&#13;
The pavgroup pointer is checked on the entrance of the function but
without the lcu-&amp;amp;gt;lock being held. Therefore there is a race window
between dasd_alias_get_start_dev() and _lcu_update() which sets
pavgroup to NULL with the lcu-&amp;amp;gt;lock held.&#13;
&#13;
Fix by checking the pavgroup pointer with lcu-&amp;amp;gt;lock held.(CVE-2022-48636)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: fix hang during unmount when stopping a space reclaim worker&#13;
&#13;
Often when running generic/562 from fstests we can hang during unmount,
resulting in a trace like this:&#13;
&#13;
  Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00
  Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.
  Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1
  Sep 07 11:55:32 debian9 kernel: &amp;amp;quot;echo 0 &amp;amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;amp;quot; disables this message.
  Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000
  Sep 07 11:55:32 debian9 kernel: Call Trace:
  Sep 07 11:55:32 debian9 kernel:  &amp;amp;lt;TASK&amp;amp;gt;
  Sep 07 11:55:32 de…&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;
s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup&#13;
&#13;
Fix Oops in dasd_alias_get_start_dev() function caused by the pavgroup
pointer being NULL.&#13;
&#13;
The pavgroup pointer is checked on the entrance of the function but
without the lcu-&amp;amp;gt;lock being held. Therefore there is a race window
between dasd_alias_get_start_dev() and _lcu_update() which sets
pavgroup to NULL with the lcu-&amp;amp;gt;lock held.&#13;
&#13;
Fix by checking the pavgroup pointer with lcu-&amp;amp;gt;lock held.(CVE-2022-48636)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: fix hang during unmount when stopping a space reclaim worker&#13;
&#13;
Often when running generic/562 from fstests we can hang during unmount,
resulting in a trace like this:&#13;
&#13;
  Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00
  Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.
  Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1
  Sep 07 11:55:32 debian9 kernel: &amp;amp;quot;echo 0 &amp;amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;amp;quot; disables this message.
  Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000
  Sep 07 11:55:32 debian9 kernel: Call Trace:
  Sep 07 11:55:32 debian9 kernel:  &amp;amp;lt;TASK&amp;amp;gt;
  Sep 07 11:55:32 de…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1651</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3983-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3983-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:3983-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48664</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48664</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 125 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix hang during unmount when stopping a space reclaim worker Often when running generic/562 from fstests we can hang during unmount, resulting in a trace like this:   Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00   Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.   Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1   Sep 07 11:55:32 debian9 kernel: &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.   Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000   Sep 07 11:55:32 debian9 kernel: Call Trace:   Sep 07 11:55:32 debian9 kernel:  &amp;lt;TASK&amp;gt;   Sep 07 11:55:32 debian9 kernel:  __schedule+0x3c8/0xec0   Sep 07 11:55:32 debian9 kernel:  ? rcu_read_lock_sched_held+0x12/0x70   Sep 07 11:55:32 debian9 kernel:  schedule+0x5d/0xf0   Sep 07 11:55:32 debian9 kernel:  schedule_timeout+0xf1/0x130   Sep 07 11:55:32 debian9 kernel:  ? lock_release+0x224/0x4a0   Sep 07 11:55:32 debian9 kernel:  ? lock_acquired+0x1a0/0x420   Sep 07 11:55:32 debian9 kernel:  ? trace_hardirqs_on+0x2c/0xd0   Sep 07 11:55:32 debian9 kernel:  __wait_for_common+0xac/0x200   Sep 07 11:55:32 debian9 kernel:  ? usleep_range_state+0xb0/0xb0   Sep 07 11:55:32 debian9 kernel:  __flush_work+0x26d/0x530   Sep 07 11:55:32 debian9 kernel:  ? flush_workqueue_prep_pwqs+0x14…&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: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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 125 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix hang during unmount when stopping a space reclaim worker Often when running generic/562 from fstests we can hang during unmount, resulting in a trace like this:   Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00   Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds.   Sep 07 11:55:32 debian9 kernel:       Not tainted 6.0.0-rc2-btrfs-next-122 #1   Sep 07 11:55:32 debian9 kernel: &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.   Sep 07 11:55:32 debian9 kernel: task:umount          state:D stack:    0 pid:49438 ppid: 25683 flags:0x00004000   Sep 07 11:55:32 debian9 kernel: Call Trace:   Sep 07 11:55:32 debian9 kernel:  &amp;lt;TASK&amp;gt;   Sep 07 11:55:32 debian9 kernel:  __schedule+0x3c8/0xec0   Sep 07 11:55:32 debian9 kernel:  ? rcu_read_lock_sched_held+0x12/0x70   Sep 07 11:55:32 debian9 kernel:  schedule+0x5d/0xf0   Sep 07 11:55:32 debian9 kernel:  schedule_timeout+0xf1/0x130   Sep 07 11:55:32 debian9 kernel:  ? lock_release+0x224/0x4a0   Sep 07 11:55:32 debian9 kernel:  ? lock_acquired+0x1a0/0x420   Sep 07 11:55:32 debian9 kernel:  ? trace_hardirqs_on+0x2c/0xd0   Sep 07 11:55:32 debian9 kernel:  __wait_for_common+0xac/0x200   Sep 07 11:55:32 debian9 kernel:  ? usleep_range_state+0xb0/0xb0   Sep 07 11:55:32 debian9 kernel:  __flush_work+0x26d/0x530   Sep 07 11:55:32 debian9 kernel:  ? flush_workqueue_prep_pwqs+0x14…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48664</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0984 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0984</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann diese Schwachstellen 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 diese Schwachstellen 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-0984</guid>
    </item>
  </channel>
</rss>
