<?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>Mon, 05 Oct 2026 10:17:59 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03019</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03019</link>
      <description>bdu:2025-03019</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03019</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-41054</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-41054</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-41054</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0957 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0957</link>
      <description>certfr-2024-avi-0957</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0957</guid>
    </item>
    <item>
      <title>EUVD-2026-312996</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312996</link>
      <description>EUVD-2026-312996</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312996</guid>
    </item>
    <item>
      <title>fkie_cve-2024-41054</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-41054</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: ufs: core: Fix ufshcd_clear_cmd racing issue&lt;/p&gt;
&lt;p&gt;When ufshcd_clear_cmd is racing with the completion ISR, the completed tag
of the request&amp;#39;s mq_hctx pointer will be set to NULL by the ISR.  And
ufshcd_clear_cmd&amp;#39;s call to ufshcd_mcq_req_to_hwq will get NULL pointer KE.
Return success when the request is completed by ISR because sq does not
need cleanup.&lt;/p&gt;
&lt;p&gt;The racing flow is:&lt;/p&gt;
&lt;p&gt;Thread A
ufshcd_err_handler					step 1
	ufshcd_try_to_abort_task
		ufshcd_cmd_inflight(true)		step 3
		ufshcd_clear_cmd
			...
			ufshcd_mcq_req_to_hwq
			blk_mq_unique_tag
				rq-&amp;gt;mq_hctx-&amp;gt;queue_num	step 5&lt;/p&gt;
&lt;p&gt;Thread B
ufs_mtk_mcq_intr(cq complete ISR)			step 2
	scsi_done
		...
		__blk_mq_free_request
			rq-&amp;gt;mq_hctx = NULL;		step 4&lt;/p&gt;
&lt;p&gt;Below is KE back trace:&lt;/p&gt;
&lt;p&gt;ufshcd_try_to_abort_task: cmd pending in the device. tag = 6
  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194
   pc : [0xffffffd589679bf8] blk_mq_unique_tag+0x8/0x14
   lr : [0xffffffd5862f95b4] ufshcd_mcq_sq_cleanup+0x6c/0x1cc [ufs_mediatek_mod_ise]
   Workqueue: ufs_eh_wq_0 ufshcd_err_handler [ufs_mediatek_mod_ise]
   Call trace:
    dump_backtrace+0xf8/0x148
    show_stack+0x18/0x24
    dump_stack_lvl+0x60/0x7c
    dump_stack+0x18/0x3c
    mrdump_common_die+0x24c/0x398 [mrdump]
    ipanic_die+0x20/0x34 [mrdump]
    notify_die+0x80/0xd8
    die+0x94/0x2b8
    __do_kernel_fault+0x264/0x298
    do_page_fault+0xa4/0x4b8
    do_translation_fault+…&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;scsi: ufs: core: Fix ufshcd_clear_cmd racing issue&lt;/p&gt;
&lt;p&gt;When ufshcd_clear_cmd is racing with the completion ISR, the completed tag
of the request&amp;#39;s mq_hctx pointer will be set to NULL by the ISR.  And
ufshcd_clear_cmd&amp;#39;s call to ufshcd_mcq_req_to_hwq will get NULL pointer KE.
Return success when the request is completed by ISR because sq does not
need cleanup.&lt;/p&gt;
&lt;p&gt;The racing flow is:&lt;/p&gt;
&lt;p&gt;Thread A
ufshcd_err_handler					step 1
	ufshcd_try_to_abort_task
		ufshcd_cmd_inflight(true)		step 3
		ufshcd_clear_cmd
			...
			ufshcd_mcq_req_to_hwq
			blk_mq_unique_tag
				rq-&amp;gt;mq_hctx-&amp;gt;queue_num	step 5&lt;/p&gt;
&lt;p&gt;Thread B
ufs_mtk_mcq_intr(cq complete ISR)			step 2
	scsi_done
		...
		__blk_mq_free_request
			rq-&amp;gt;mq_hctx = NULL;		step 4&lt;/p&gt;
&lt;p&gt;Below is KE back trace:&lt;/p&gt;
&lt;p&gt;ufshcd_try_to_abort_task: cmd pending in the device. tag = 6
  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194
   pc : [0xffffffd589679bf8] blk_mq_unique_tag+0x8/0x14
   lr : [0xffffffd5862f95b4] ufshcd_mcq_sq_cleanup+0x6c/0x1cc [ufs_mediatek_mod_ise]
   Workqueue: ufs_eh_wq_0 ufshcd_err_handler [ufs_mediatek_mod_ise]
   Call trace:
    dump_backtrace+0xf8/0x148
    show_stack+0x18/0x24
    dump_stack_lvl+0x60/0x7c
    dump_stack+0x18/0x3c
    mrdump_common_die+0x24c/0x398 [mrdump]
    ipanic_die+0x20/0x34 [mrdump]
    notify_die+0x80/0xd8
    die+0x94/0x2b8
    __do_kernel_fault+0x264/0x298
    do_page_fault+0xa4/0x4b8
    do_translation_fault+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-41054</guid>
    </item>
    <item>
      <title>GHSA-7f9h-6jq6-8gmx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7f9h-6jq6-8gmx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: ufs: core: Fix ufshcd_clear_cmd racing issue&lt;/p&gt;
&lt;p&gt;When ufshcd_clear_cmd is racing with the completion ISR, the completed tag
of the request&amp;#39;s mq_hctx pointer will be set to NULL by the ISR.  And
ufshcd_clear_cmd&amp;#39;s call to ufshcd_mcq_req_to_hwq will get NULL pointer KE.
Return success when the request is completed by ISR because sq does not
need cleanup.&lt;/p&gt;
&lt;p&gt;The racing flow is:&lt;/p&gt;
&lt;p&gt;Thread A
ufshcd_err_handler					step 1
	ufshcd_try_to_abort_task
		ufshcd_cmd_inflight(true)		step 3
		ufshcd_clear_cmd
			...
			ufshcd_mcq_req_to_hwq
			blk_mq_unique_tag
				rq-&amp;gt;mq_hctx-&amp;gt;queue_num	step 5&lt;/p&gt;
&lt;p&gt;Thread B
ufs_mtk_mcq_intr(cq complete ISR)			step 2
	scsi_done
		...
		__blk_mq_free_request
			rq-&amp;gt;mq_hctx = NULL;		step 4&lt;/p&gt;
&lt;p&gt;Below is KE back trace:&lt;/p&gt;
&lt;p&gt;ufshcd_try_to_abort_task: cmd pending in the device. tag = 6
  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194
   pc : [0xffffffd589679bf8] blk_mq_unique_tag+0x8/0x14
   lr : [0xffffffd5862f95b4] ufshcd_mcq_sq_cleanup+0x6c/0x1cc [ufs_mediatek_mod_ise]
   Workqueue: ufs_eh_wq_0 ufshcd_err_handler [ufs_mediatek_mod_ise]
   Call trace:
    dump_backtrace+0xf8/0x148
    show_stack+0x18/0x24
    dump_stack_lvl+0x60/0x7c
    dump_stack+0x18/0x3c
    mrdump_common_die+0x24c/0x398 [mrdump]
    ipanic_die+0x20/0x34 [mrdump]
    notify_die+0x80/0xd8
    die+0x94/0x2b8
    __do_kernel_fault+0x264/0x298
    do_page_fault+0xa4/0x4b8
    do_translation_fault+…&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;scsi: ufs: core: Fix ufshcd_clear_cmd racing issue&lt;/p&gt;
&lt;p&gt;When ufshcd_clear_cmd is racing with the completion ISR, the completed tag
of the request&amp;#39;s mq_hctx pointer will be set to NULL by the ISR.  And
ufshcd_clear_cmd&amp;#39;s call to ufshcd_mcq_req_to_hwq will get NULL pointer KE.
Return success when the request is completed by ISR because sq does not
need cleanup.&lt;/p&gt;
&lt;p&gt;The racing flow is:&lt;/p&gt;
&lt;p&gt;Thread A
ufshcd_err_handler					step 1
	ufshcd_try_to_abort_task
		ufshcd_cmd_inflight(true)		step 3
		ufshcd_clear_cmd
			...
			ufshcd_mcq_req_to_hwq
			blk_mq_unique_tag
				rq-&amp;gt;mq_hctx-&amp;gt;queue_num	step 5&lt;/p&gt;
&lt;p&gt;Thread B
ufs_mtk_mcq_intr(cq complete ISR)			step 2
	scsi_done
		...
		__blk_mq_free_request
			rq-&amp;gt;mq_hctx = NULL;		step 4&lt;/p&gt;
&lt;p&gt;Below is KE back trace:&lt;/p&gt;
&lt;p&gt;ufshcd_try_to_abort_task: cmd pending in the device. tag = 6
  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194
   pc : [0xffffffd589679bf8] blk_mq_unique_tag+0x8/0x14
   lr : [0xffffffd5862f95b4] ufshcd_mcq_sq_cleanup+0x6c/0x1cc [ufs_mediatek_mod_ise]
   Workqueue: ufs_eh_wq_0 ufshcd_err_handler [ufs_mediatek_mod_ise]
   Call trace:
    dump_backtrace+0xf8/0x148
    show_stack+0x18/0x24
    dump_stack_lvl+0x60/0x7c
    dump_stack+0x18/0x3c
    mrdump_common_die+0x24c/0x398 [mrdump]
    ipanic_die+0x20/0x34 [mrdump]
    notify_die+0x80/0xd8
    die+0x94/0x2b8
    __do_kernel_fault+0x264/0x298
    do_page_fault+0xa4/0x4b8
    do_translation_fault+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7f9h-6jq6-8gmx</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-41054 — scsi: ufs: core: Fix ufshcd_clear_cmd racing issue</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-41054</link>
      <description>msrc_CVE-2024-41054</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-41054</guid>
    </item>
    <item>
      <title>OESA-2024-2076 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2076</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
ipvlan: Dont Use skb-&amp;amp;gt;sk in ipvlan_process_v{4,6}_outbound&#13;
&#13;
Raw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will
hit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.&#13;
&#13;
WARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70
Modules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper
CPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
RIP: 0010:sk_mc_loop+0x2d/0x70
Code: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c
RSP: 0018:ffffa9584015cd78 EFLAGS: 00010212
RAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001
RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000
RBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00
R10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000
R13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000
FS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
&amp;amp;lt;IRQ&amp;amp;gt;
 ?…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
ipvlan: Dont Use skb-&amp;amp;gt;sk in ipvlan_process_v{4,6}_outbound&#13;
&#13;
Raw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will
hit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.&#13;
&#13;
WARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70
Modules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper
CPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
RIP: 0010:sk_mc_loop+0x2d/0x70
Code: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c
RSP: 0018:ffffa9584015cd78 EFLAGS: 00010212
RAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001
RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000
RBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00
R10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000
R13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000
FS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
&amp;amp;lt;IRQ&amp;amp;gt;
 ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2076</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-41054</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41054</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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix ufshcd_clear_cmd racing issue When ufshcd_clear_cmd is racing with the completion ISR, the completed tag of the request&amp;#39;s mq_hctx pointer will be set to NULL by the ISR.  And ufshcd_clear_cmd&amp;#39;s call to ufshcd_mcq_req_to_hwq will get NULL pointer KE. Return success when the request is completed by ISR because sq does not need cleanup. The racing flow is: Thread A ufshcd_err_handler					step 1 	ufshcd_try_to_abort_task 		ufshcd_cmd_inflight(true)		step 3 		ufshcd_clear_cmd 			... 			ufshcd_mcq_req_to_hwq 			blk_mq_unique_tag 				rq-&amp;gt;mq_hctx-&amp;gt;queue_num	step 5 Thread B ufs_mtk_mcq_intr(cq complete ISR)			step 2 	scsi_done 		... 		__blk_mq_free_request 			rq-&amp;gt;mq_hctx = NULL;		step 4 Below is KE back trace:   ufshcd_try_to_abort_task: cmd pending in the device. tag = 6   Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194    pc : [0xffffffd589679bf8] blk_mq_unique_tag+0x8/0x14    lr : [0xffffffd5862f95b4] ufshcd_mcq_sq_cleanup+0x6c/0x1cc [ufs_mediatek_mod_ise]    Workqueue: ufs_eh_wq_0 ufshcd_err_handler [ufs_mediatek_mod_ise]    Call trace:     dump_backtrace+0xf8/0x148     show_stack+0x18/0x24     dump_stack_lvl+0x60/0x7c     dump_stack+0x18/0x3c     mrdump_common_die+0x24c/0x398 [mrdump]     ipanic_die+0x20/0x34 [mrdump]     notify_die+0x80/0xd8     die+0x94/0x2b8     __do_kernel_fault+0x264/0x298     do_page_fault+0xa4/0x4b8     do_translation_fault+0x38/0x…&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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix ufshcd_clear_cmd racing issue When ufshcd_clear_cmd is racing with the completion ISR, the completed tag of the request&amp;#39;s mq_hctx pointer will be set to NULL by the ISR.  And ufshcd_clear_cmd&amp;#39;s call to ufshcd_mcq_req_to_hwq will get NULL pointer KE. Return success when the request is completed by ISR because sq does not need cleanup. The racing flow is: Thread A ufshcd_err_handler					step 1 	ufshcd_try_to_abort_task 		ufshcd_cmd_inflight(true)		step 3 		ufshcd_clear_cmd 			... 			ufshcd_mcq_req_to_hwq 			blk_mq_unique_tag 				rq-&amp;gt;mq_hctx-&amp;gt;queue_num	step 5 Thread B ufs_mtk_mcq_intr(cq complete ISR)			step 2 	scsi_done 		... 		__blk_mq_free_request 			rq-&amp;gt;mq_hctx = NULL;		step 4 Below is KE back trace:   ufshcd_try_to_abort_task: cmd pending in the device. tag = 6   Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194    pc : [0xffffffd589679bf8] blk_mq_unique_tag+0x8/0x14    lr : [0xffffffd5862f95b4] ufshcd_mcq_sq_cleanup+0x6c/0x1cc [ufs_mediatek_mod_ise]    Workqueue: ufs_eh_wq_0 ufshcd_err_handler [ufs_mediatek_mod_ise]    Call trace:     dump_backtrace+0xf8/0x148     show_stack+0x18/0x24     dump_stack_lvl+0x60/0x7c     dump_stack+0x18/0x3c     mrdump_common_die+0x24c/0x398 [mrdump]     ipanic_die+0x20/0x34 [mrdump]     notify_die+0x80/0xd8     die+0x94/0x2b8     __do_kernel_fault+0x264/0x298     do_page_fault+0xa4/0x4b8     do_translation_fault+0x38/0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41054</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1722 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1722</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1722</guid>
    </item>
  </channel>
</rss>
