<?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 17:15:08 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-06047</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-06047</link>
      <description>bdu:2026-06047</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-06047</guid>
    </item>
    <item>
      <title>EUVD-2026-311080</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311080</link>
      <description>EUVD-2026-311080</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311080</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50193</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50193</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;erofs: wake up all waiters after z_erofs_lzma_head ready&lt;/p&gt;
&lt;p&gt;When the user mounts the erofs second times, the decompression thread
may hung. The problem happens due to a sequence of steps like the
following:&lt;/p&gt;
&lt;p&gt;1) Task A called z_erofs_load_lzma_config which obtain all of the node
   from the z_erofs_lzma_head.&lt;/p&gt;
&lt;p&gt;2) At this time, task B called the z_erofs_lzma_decompress and wanted to
   get a node. But the z_erofs_lzma_head was empty, the Task B had to
   sleep.&lt;/p&gt;
&lt;p&gt;3) Task A release nodes and push nodes into the z_erofs_lzma_head. But
   task B was still sleeping.&lt;/p&gt;
&lt;p&gt;One example report when the hung happens:
task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000
Workqueue: erofs_unzipd z_erofs_decompressqueue_work
Call Trace:
 &amp;lt;TASK&amp;gt;
 __schedule+0x281/0x760
 schedule+0x49/0xb0
 z_erofs_lzma_decompress+0x4bc/0x580
 ? cpu_core_flags+0x10/0x10
 z_erofs_decompress_pcluster+0x49b/0xba0
 ? __update_load_avg_se+0x2b0/0x330
 ? __update_load_avg_se+0x2b0/0x330
 ? update_load_avg+0x5f/0x690
 ? update_load_avg+0x5f/0x690
 ? set_next_entity+0xbd/0x110
 ? _raw_spin_unlock+0xd/0x20
 z_erofs_decompress_queue.isra.0+0x2e/0x50
 z_erofs_decompressqueue_work+0x30/0x60
 process_one_work+0x1d3/0x3a0
 worker_thread+0x45/0x3a0
 ? process_one_work+0x3a0/0x3a0
 kthread+0xe2/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x22/0x30
 &amp;lt;/TASK&amp;gt;&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;erofs: wake up all waiters after z_erofs_lzma_head ready&lt;/p&gt;
&lt;p&gt;When the user mounts the erofs second times, the decompression thread
may hung. The problem happens due to a sequence of steps like the
following:&lt;/p&gt;
&lt;p&gt;1) Task A called z_erofs_load_lzma_config which obtain all of the node
   from the z_erofs_lzma_head.&lt;/p&gt;
&lt;p&gt;2) At this time, task B called the z_erofs_lzma_decompress and wanted to
   get a node. But the z_erofs_lzma_head was empty, the Task B had to
   sleep.&lt;/p&gt;
&lt;p&gt;3) Task A release nodes and push nodes into the z_erofs_lzma_head. But
   task B was still sleeping.&lt;/p&gt;
&lt;p&gt;One example report when the hung happens:
task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000
Workqueue: erofs_unzipd z_erofs_decompressqueue_work
Call Trace:
 &amp;lt;TASK&amp;gt;
 __schedule+0x281/0x760
 schedule+0x49/0xb0
 z_erofs_lzma_decompress+0x4bc/0x580
 ? cpu_core_flags+0x10/0x10
 z_erofs_decompress_pcluster+0x49b/0xba0
 ? __update_load_avg_se+0x2b0/0x330
 ? __update_load_avg_se+0x2b0/0x330
 ? update_load_avg+0x5f/0x690
 ? update_load_avg+0x5f/0x690
 ? set_next_entity+0xbd/0x110
 ? _raw_spin_unlock+0xd/0x20
 z_erofs_decompress_queue.isra.0+0x2e/0x50
 z_erofs_decompressqueue_work+0x30/0x60
 process_one_work+0x1d3/0x3a0
 worker_thread+0x45/0x3a0
 ? process_one_work+0x3a0/0x3a0
 kthread+0xe2/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x22/0x30
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50193</guid>
    </item>
    <item>
      <title>GHSA-9244-ghq8-mvq4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9244-ghq8-mvq4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;erofs: wake up all waiters after z_erofs_lzma_head ready&lt;/p&gt;
&lt;p&gt;When the user mounts the erofs second times, the decompression thread
may hung. The problem happens due to a sequence of steps like the
following:&lt;/p&gt;
&lt;p&gt;1) Task A called z_erofs_load_lzma_config which obtain all of the node
   from the z_erofs_lzma_head.&lt;/p&gt;
&lt;p&gt;2) At this time, task B called the z_erofs_lzma_decompress and wanted to
   get a node. But the z_erofs_lzma_head was empty, the Task B had to
   sleep.&lt;/p&gt;
&lt;p&gt;3) Task A release nodes and push nodes into the z_erofs_lzma_head. But
   task B was still sleeping.&lt;/p&gt;
&lt;p&gt;One example report when the hung happens:
task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000
Workqueue: erofs_unzipd z_erofs_decompressqueue_work
Call Trace:
 &amp;lt;TASK&amp;gt;
 __schedule+0x281/0x760
 schedule+0x49/0xb0
 z_erofs_lzma_decompress+0x4bc/0x580
 ? cpu_core_flags+0x10/0x10
 z_erofs_decompress_pcluster+0x49b/0xba0
 ? __update_load_avg_se+0x2b0/0x330
 ? __update_load_avg_se+0x2b0/0x330
 ? update_load_avg+0x5f/0x690
 ? update_load_avg+0x5f/0x690
 ? set_next_entity+0xbd/0x110
 ? _raw_spin_unlock+0xd/0x20
 z_erofs_decompress_queue.isra.0+0x2e/0x50
 z_erofs_decompressqueue_work+0x30/0x60
 process_one_work+0x1d3/0x3a0
 worker_thread+0x45/0x3a0
 ? process_one_work+0x3a0/0x3a0
 kthread+0xe2/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x22/0x30
 &amp;lt;/TASK&amp;gt;&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;erofs: wake up all waiters after z_erofs_lzma_head ready&lt;/p&gt;
&lt;p&gt;When the user mounts the erofs second times, the decompression thread
may hung. The problem happens due to a sequence of steps like the
following:&lt;/p&gt;
&lt;p&gt;1) Task A called z_erofs_load_lzma_config which obtain all of the node
   from the z_erofs_lzma_head.&lt;/p&gt;
&lt;p&gt;2) At this time, task B called the z_erofs_lzma_decompress and wanted to
   get a node. But the z_erofs_lzma_head was empty, the Task B had to
   sleep.&lt;/p&gt;
&lt;p&gt;3) Task A release nodes and push nodes into the z_erofs_lzma_head. But
   task B was still sleeping.&lt;/p&gt;
&lt;p&gt;One example report when the hung happens:
task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000
Workqueue: erofs_unzipd z_erofs_decompressqueue_work
Call Trace:
 &amp;lt;TASK&amp;gt;
 __schedule+0x281/0x760
 schedule+0x49/0xb0
 z_erofs_lzma_decompress+0x4bc/0x580
 ? cpu_core_flags+0x10/0x10
 z_erofs_decompress_pcluster+0x49b/0xba0
 ? __update_load_avg_se+0x2b0/0x330
 ? __update_load_avg_se+0x2b0/0x330
 ? update_load_avg+0x5f/0x690
 ? update_load_avg+0x5f/0x690
 ? set_next_entity+0xbd/0x110
 ? _raw_spin_unlock+0xd/0x20
 z_erofs_decompress_queue.isra.0+0x2e/0x50
 z_erofs_decompressqueue_work+0x30/0x60
 process_one_work+0x1d3/0x3a0
 worker_thread+0x45/0x3a0
 ? process_one_work+0x3a0/0x3a0
 kthread+0xe2/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x22/0x30
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9244-ghq8-mvq4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50193</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50193</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: erofs: wake up all waiters after z_erofs_lzma_head ready When the user mounts the erofs second times, the decompression thread may hung. The problem happens due to a sequence of steps like the following: 1) Task A called z_erofs_load_lzma_config which obtain all of the node    from the z_erofs_lzma_head. 2) At this time, task B called the z_erofs_lzma_decompress and wanted to    get a node. But the z_erofs_lzma_head was empty, the Task B had to    sleep. 3) Task A release nodes and push nodes into the z_erofs_lzma_head. But    task B was still sleeping. One example report when the hung happens: task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000 Workqueue: erofs_unzipd z_erofs_decompressqueue_work Call Trace:  &amp;lt;TASK&amp;gt;  __schedule+0x281/0x760  schedule+0x49/0xb0  z_erofs_lzma_decompress+0x4bc/0x580  ? cpu_core_flags+0x10/0x10  z_erofs_decompress_pcluster+0x49b/0xba0  ? __update_load_avg_se+0x2b0/0x330  ? __update_load_avg_se+0x2b0/0x330  ? update_load_avg+0x5f/0x690  ? update_load_avg+0x5f/0x690  ? set_next_entity+0xbd/0x110  ? _raw_spin_unlock+0xd/0x20  z_erofs_decompress_queue.isra.0+0x2e/0x50  z_erofs_decompressqueue_work+0x30/0x60  process_one_work+0x1d3/0x3a0  worker_thread+0x45/0x3a0  ? process_one_work+0x3a0/0x3a0  kthread+0xe2/0x110  ? kthread_complete_and_exit+0x20/0x20  ret_from_fork+0x22/0x30  &amp;lt;/TASK&amp;gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: erofs: wake up all waiters after z_erofs_lzma_head ready When the user mounts the erofs second times, the decompression thread may hung. The problem happens due to a sequence of steps like the following: 1) Task A called z_erofs_load_lzma_config which obtain all of the node    from the z_erofs_lzma_head. 2) At this time, task B called the z_erofs_lzma_decompress and wanted to    get a node. But the z_erofs_lzma_head was empty, the Task B had to    sleep. 3) Task A release nodes and push nodes into the z_erofs_lzma_head. But    task B was still sleeping. One example report when the hung happens: task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000 Workqueue: erofs_unzipd z_erofs_decompressqueue_work Call Trace:  &amp;lt;TASK&amp;gt;  __schedule+0x281/0x760  schedule+0x49/0xb0  z_erofs_lzma_decompress+0x4bc/0x580  ? cpu_core_flags+0x10/0x10  z_erofs_decompress_pcluster+0x49b/0xba0  ? __update_load_avg_se+0x2b0/0x330  ? __update_load_avg_se+0x2b0/0x330  ? update_load_avg+0x5f/0x690  ? update_load_avg+0x5f/0x690  ? set_next_entity+0xbd/0x110  ? _raw_spin_unlock+0xd/0x20  z_erofs_decompress_queue.isra.0+0x2e/0x50  z_erofs_decompressqueue_work+0x30/0x60  process_one_work+0x1d3/0x3a0  worker_thread+0x45/0x3a0  ? process_one_work+0x3a0/0x3a0  kthread+0xe2/0x110  ? kthread_complete_and_exit+0x20/0x20  ret_from_fork+0x22/0x30  &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50193</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
