<?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 11:51:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03710</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03710</link>
      <description>bdu:2024-03710</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03710</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0420 — 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-0420</link>
      <description>certfr-2024-avi-0420</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0420</guid>
    </item>
    <item>
      <title>cnvd-2024-24973</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-24973</link>
      <description>cnvd-2024-24973</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-24973</guid>
    </item>
    <item>
      <title>EUVD-2026-344547</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344547</link>
      <description>EUVD-2026-344547</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344547</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48658</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48658</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.&lt;/p&gt;
&lt;p&gt;Commit 5a836bf6b09f (&amp;#34;mm: slub: move flush_cpu_slab() invocations
__free_slab() invocations out of IRQ context&amp;#34;) moved all flush_cpu_slab()
invocations to the global workqueue to avoid a problem related
with deactivate_slab()/__free_slab() being called from an IRQ context
on PREEMPT_RT kernels.&lt;/p&gt;
&lt;p&gt;When the flush_all_cpu_locked() function is called from a task context
it may happen that a workqueue with WQ_MEM_RECLAIM bit set ends up
flushing the global workqueue, this will cause a dependency issue.&lt;/p&gt;
&lt;p&gt;workqueue: WQ_MEM_RECLAIM nvme-delete-wq:nvme_delete_ctrl_work [nvme_core]
   is flushing !WQ_MEM_RECLAIM events:flush_cpu_slab
 WARNING: CPU: 37 PID: 410 at kernel/workqueue.c:2637
   check_flush_dependency+0x10a/0x120
 Workqueue: nvme-delete-wq nvme_delete_ctrl_work [nvme_core]
 RIP: 0010:check_flush_dependency+0x10a/0x120[  453.262125] Call Trace:
 __flush_work.isra.0+0xbf/0x220
 ? __queue_work+0x1dc/0x420
 flush_all_cpus_locked+0xfb/0x120
 __kmem_cache_shutdown+0x2b/0x320
 kmem_cache_destroy+0x49/0x100
 bioset_exit+0x143/0x190
 blk_release_queue+0xb9/0x100
 kobject_cleanup+0x37/0x130
 nvme_fc_ctrl_free+0xc6/0x150 [nvme_fc]
 nvme_free_ctrl+0x1ac/0x2b0 [nvme_core]&lt;/p&gt;
&lt;p&gt;Fix this bug by creating a workqueue for the flush operation with
the WQ_MEM_RECLAIM bit set.&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;mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.&lt;/p&gt;
&lt;p&gt;Commit 5a836bf6b09f (&amp;#34;mm: slub: move flush_cpu_slab() invocations
__free_slab() invocations out of IRQ context&amp;#34;) moved all flush_cpu_slab()
invocations to the global workqueue to avoid a problem related
with deactivate_slab()/__free_slab() being called from an IRQ context
on PREEMPT_RT kernels.&lt;/p&gt;
&lt;p&gt;When the flush_all_cpu_locked() function is called from a task context
it may happen that a workqueue with WQ_MEM_RECLAIM bit set ends up
flushing the global workqueue, this will cause a dependency issue.&lt;/p&gt;
&lt;p&gt;workqueue: WQ_MEM_RECLAIM nvme-delete-wq:nvme_delete_ctrl_work [nvme_core]
   is flushing !WQ_MEM_RECLAIM events:flush_cpu_slab
 WARNING: CPU: 37 PID: 410 at kernel/workqueue.c:2637
   check_flush_dependency+0x10a/0x120
 Workqueue: nvme-delete-wq nvme_delete_ctrl_work [nvme_core]
 RIP: 0010:check_flush_dependency+0x10a/0x120[  453.262125] Call Trace:
 __flush_work.isra.0+0xbf/0x220
 ? __queue_work+0x1dc/0x420
 flush_all_cpus_locked+0xfb/0x120
 __kmem_cache_shutdown+0x2b/0x320
 kmem_cache_destroy+0x49/0x100
 bioset_exit+0x143/0x190
 blk_release_queue+0xb9/0x100
 kobject_cleanup+0x37/0x130
 nvme_fc_ctrl_free+0xc6/0x150 [nvme_fc]
 nvme_free_ctrl+0x1ac/0x2b0 [nvme_core]&lt;/p&gt;
&lt;p&gt;Fix this bug by creating a workqueue for the flush operation with
the WQ_MEM_RECLAIM bit set.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48658</guid>
    </item>
    <item>
      <title>GHSA-qr7h-9g6j-jwg3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qr7h-9g6j-jwg3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.&lt;/p&gt;
&lt;p&gt;Commit 5a836bf6b09f (&amp;#34;mm: slub: move flush_cpu_slab() invocations
__free_slab() invocations out of IRQ context&amp;#34;) moved all flush_cpu_slab()
invocations to the global workqueue to avoid a problem related
with deactivate_slab()/__free_slab() being called from an IRQ context
on PREEMPT_RT kernels.&lt;/p&gt;
&lt;p&gt;When the flush_all_cpu_locked() function is called from a task context
it may happen that a workqueue with WQ_MEM_RECLAIM bit set ends up
flushing the global workqueue, this will cause a dependency issue.&lt;/p&gt;
&lt;p&gt;workqueue: WQ_MEM_RECLAIM nvme-delete-wq:nvme_delete_ctrl_work [nvme_core]
   is flushing !WQ_MEM_RECLAIM events:flush_cpu_slab
 WARNING: CPU: 37 PID: 410 at kernel/workqueue.c:2637
   check_flush_dependency+0x10a/0x120
 Workqueue: nvme-delete-wq nvme_delete_ctrl_work [nvme_core]
 RIP: 0010:check_flush_dependency+0x10a/0x120[  453.262125] Call Trace:
 __flush_work.isra.0+0xbf/0x220
 ? __queue_work+0x1dc/0x420
 flush_all_cpus_locked+0xfb/0x120
 __kmem_cache_shutdown+0x2b/0x320
 kmem_cache_destroy+0x49/0x100
 bioset_exit+0x143/0x190
 blk_release_queue+0xb9/0x100
 kobject_cleanup+0x37/0x130
 nvme_fc_ctrl_free+0xc6/0x150 [nvme_fc]
 nvme_free_ctrl+0x1ac/0x2b0 [nvme_core]&lt;/p&gt;
&lt;p&gt;Fix this bug by creating a workqueue for the flush operation with
the WQ_MEM_RECLAIM bit set.&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;mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.&lt;/p&gt;
&lt;p&gt;Commit 5a836bf6b09f (&amp;#34;mm: slub: move flush_cpu_slab() invocations
__free_slab() invocations out of IRQ context&amp;#34;) moved all flush_cpu_slab()
invocations to the global workqueue to avoid a problem related
with deactivate_slab()/__free_slab() being called from an IRQ context
on PREEMPT_RT kernels.&lt;/p&gt;
&lt;p&gt;When the flush_all_cpu_locked() function is called from a task context
it may happen that a workqueue with WQ_MEM_RECLAIM bit set ends up
flushing the global workqueue, this will cause a dependency issue.&lt;/p&gt;
&lt;p&gt;workqueue: WQ_MEM_RECLAIM nvme-delete-wq:nvme_delete_ctrl_work [nvme_core]
   is flushing !WQ_MEM_RECLAIM events:flush_cpu_slab
 WARNING: CPU: 37 PID: 410 at kernel/workqueue.c:2637
   check_flush_dependency+0x10a/0x120
 Workqueue: nvme-delete-wq nvme_delete_ctrl_work [nvme_core]
 RIP: 0010:check_flush_dependency+0x10a/0x120[  453.262125] Call Trace:
 __flush_work.isra.0+0xbf/0x220
 ? __queue_work+0x1dc/0x420
 flush_all_cpus_locked+0xfb/0x120
 __kmem_cache_shutdown+0x2b/0x320
 kmem_cache_destroy+0x49/0x100
 bioset_exit+0x143/0x190
 blk_release_queue+0xb9/0x100
 kobject_cleanup+0x37/0x130
 nvme_fc_ctrl_free+0xc6/0x150 [nvme_fc]
 nvme_free_ctrl+0x1ac/0x2b0 [nvme_core]&lt;/p&gt;
&lt;p&gt;Fix this bug by creating a workqueue for the flush operation with
the WQ_MEM_RECLAIM bit set.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qr7h-9g6j-jwg3</guid>
    </item>
    <item>
      <title>gsd-2022-48658</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-48658</link>
      <description>gsd-2022-48658</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-48658</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1644-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1644-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:1644-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48658</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48658</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 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context. Commit 5a836bf6b09f (&amp;#34;mm: slub: move flush_cpu_slab() invocations __free_slab() invocations out of IRQ context&amp;#34;) moved all flush_cpu_slab() invocations to the global workqueue to avoid a problem related with deactivate_slab()/__free_slab() being called from an IRQ context on PREEMPT_RT kernels. When the flush_all_cpu_locked() function is called from a task context it may happen that a workqueue with WQ_MEM_RECLAIM bit set ends up flushing the global workqueue, this will cause a dependency issue.  workqueue: WQ_MEM_RECLAIM nvme-delete-wq:nvme_delete_ctrl_work [nvme_core]    is flushing !WQ_MEM_RECLAIM events:flush_cpu_slab  WARNING: CPU: 37 PID: 410 at kernel/workqueue.c:2637    check_flush_dependency+0x10a/0x120  Workqueue: nvme-delete-wq nvme_delete_ctrl_work [nvme_core]  RIP: 0010:check_flush_dependency+0x10a/0x120[  453.262125] Call Trace:  __flush_work.isra.0+0xbf/0x220  ? __queue_work+0x1dc/0x420  flush_all_cpus_locked+0xfb/0x120  __kmem_cache_shutdown+0x2b/0x320  kmem_cache_destroy+0x49/0x100  bioset_exit+0x143/0x190  blk_release_queue+0xb9/0x100  kobject_cleanup+0x37/0x130  nvme_fc_ctrl_free+0xc6/0x150 [nvme_fc]  nvme_free_ctrl+0x1ac/0x2b0 [nvme_core] Fix this bug by creating a workqueue for the flush operation with the WQ_MEM_RECLAIM bit set.&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 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context. Commit 5a836bf6b09f (&amp;#34;mm: slub: move flush_cpu_slab() invocations __free_slab() invocations out of IRQ context&amp;#34;) moved all flush_cpu_slab() invocations to the global workqueue to avoid a problem related with deactivate_slab()/__free_slab() being called from an IRQ context on PREEMPT_RT kernels. When the flush_all_cpu_locked() function is called from a task context it may happen that a workqueue with WQ_MEM_RECLAIM bit set ends up flushing the global workqueue, this will cause a dependency issue.  workqueue: WQ_MEM_RECLAIM nvme-delete-wq:nvme_delete_ctrl_work [nvme_core]    is flushing !WQ_MEM_RECLAIM events:flush_cpu_slab  WARNING: CPU: 37 PID: 410 at kernel/workqueue.c:2637    check_flush_dependency+0x10a/0x120  Workqueue: nvme-delete-wq nvme_delete_ctrl_work [nvme_core]  RIP: 0010:check_flush_dependency+0x10a/0x120[  453.262125] Call Trace:  __flush_work.isra.0+0xbf/0x220  ? __queue_work+0x1dc/0x420  flush_all_cpus_locked+0xfb/0x120  __kmem_cache_shutdown+0x2b/0x320  kmem_cache_destroy+0x49/0x100  bioset_exit+0x143/0x190  blk_release_queue+0xb9/0x100  kobject_cleanup+0x37/0x130  nvme_fc_ctrl_free+0xc6/0x150 [nvme_fc]  nvme_free_ctrl+0x1ac/0x2b0 [nvme_core] Fix this bug by creating a workqueue for the flush operation with the WQ_MEM_RECLAIM bit set.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48658</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>
