<?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>Sun, 04 Oct 2026 01:22:05 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01204</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-01204</link>
      <description>bdu:2026-01204</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-01204</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-54153</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-54153</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-54153</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — 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-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-345396</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345396</link>
      <description>EUVD-2026-345396</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345396</guid>
    </item>
    <item>
      <title>fkie_cve-2023-54153</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-54153</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;
&lt;p&gt;Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent
journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error
value, the error handling path does not turn off the enabled quotas,
which triggers the following kmemleak:&lt;/p&gt;
&lt;p&gt;================================================================
unreferenced object 0xffff8cf68678e7c0 (size 64):
comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s)
hex dump (first 32 bytes):
00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A...
c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H...
backtrace:
[&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880
[&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140
[&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0
[&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770
[&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0
[&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4]
[&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4]
[&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4]
[&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370
[&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4]
[&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160
[&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480
[&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0
[&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0
[&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160
[&amp;lt;0000000027d21…&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;ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;
&lt;p&gt;Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent
journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error
value, the error handling path does not turn off the enabled quotas,
which triggers the following kmemleak:&lt;/p&gt;
&lt;p&gt;================================================================
unreferenced object 0xffff8cf68678e7c0 (size 64):
comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s)
hex dump (first 32 bytes):
00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A...
c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H...
backtrace:
[&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880
[&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140
[&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0
[&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770
[&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0
[&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4]
[&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4]
[&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4]
[&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370
[&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4]
[&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160
[&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480
[&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0
[&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0
[&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160
[&amp;lt;0000000027d21…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-54153</guid>
    </item>
    <item>
      <title>GHSA-969x-jvv9-7j58</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-969x-jvv9-7j58</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;
&lt;p&gt;Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent
journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error
value, the error handling path does not turn off the enabled quotas,
which triggers the following kmemleak:&lt;/p&gt;
&lt;p&gt;================================================================
unreferenced object 0xffff8cf68678e7c0 (size 64):
comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s)
hex dump (first 32 bytes):
00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A...
c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H...
backtrace:
[&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880
[&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140
[&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0
[&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770
[&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0
[&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4]
[&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4]
[&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4]
[&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370
[&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4]
[&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160
[&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480
[&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0
[&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0
[&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160
[&amp;lt;0000000027d21…&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;ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;
&lt;p&gt;Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent
journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error
value, the error handling path does not turn off the enabled quotas,
which triggers the following kmemleak:&lt;/p&gt;
&lt;p&gt;================================================================
unreferenced object 0xffff8cf68678e7c0 (size 64):
comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s)
hex dump (first 32 bytes):
00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A...
c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H...
backtrace:
[&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880
[&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140
[&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0
[&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770
[&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0
[&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4]
[&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4]
[&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4]
[&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370
[&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4]
[&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160
[&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480
[&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0
[&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0
[&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160
[&amp;lt;0000000027d21…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-969x-jvv9-7j58</guid>
    </item>
    <item>
      <title>RHBA-2024:9014 — Red Hat Bug Fix Advisory: updated el9/flatpak-sdk container image</title>
      <link>https://cve.radiocsirt.org/vuln/rhba-2024:9014</link>
      <description>&lt;p&gt;kernel: ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhba-2024:9014</guid>
    </item>
    <item>
      <title>RHSA-2024:8617 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:8617</link>
      <description>&lt;p&gt;kernel: tty: Fix out-of-bound vmalloc access in imageblit kernel: ext4: turn quotas off if mount failed after enabling quotas hw: cpu: intel: Native Branch History Injection (BHI) kernel: tcp: add sanity checks to rx zerocopy kernel: mptcp: fix data re-injection from stale subflow kernel: af_unix: Fix garbage collector racing against connect() kernel: scsi: core: Fix unremoved procfs host directory regression kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del kernel: net/sched: taprio: extend minimum interval restriction to entire cycle too kernel: xfs: fix log recovery buffer allocation for the legacy h_size fixup kernel: netfilter: nft_inner: validate mandatory meta and payload kernel: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages kernel: mptcp: ensure snd_una is properly initialized on connect kernel: ipv6: prevent possible NULL dereference in rt6_probe() kernel: ext4: do not create EA inode under buffer lock kernel: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery kernel: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() kernel: ext4: fix uninitialized ratelimit_state-&amp;amp;gt;lock access in __ext4_fill_super() kernel: netpoll: Fix race condition in netpoll_owner_active kernel: xfs: don&amp;amp;#39;t walk off the end of a directory data block kernel: xfs: add bounds checking to xlog_recover_process_data kernel: block: initialize integrity buffer to zero before writing it to media kernel: netfilt…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: tty: Fix out-of-bound vmalloc access in imageblit kernel: ext4: turn quotas off if mount failed after enabling quotas hw: cpu: intel: Native Branch History Injection (BHI) kernel: tcp: add sanity checks to rx zerocopy kernel: mptcp: fix data re-injection from stale subflow kernel: af_unix: Fix garbage collector racing against connect() kernel: scsi: core: Fix unremoved procfs host directory regression kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del kernel: net/sched: taprio: extend minimum interval restriction to entire cycle too kernel: xfs: fix log recovery buffer allocation for the legacy h_size fixup kernel: netfilter: nft_inner: validate mandatory meta and payload kernel: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages kernel: mptcp: ensure snd_una is properly initialized on connect kernel: ipv6: prevent possible NULL dereference in rt6_probe() kernel: ext4: do not create EA inode under buffer lock kernel: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery kernel: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() kernel: ext4: fix uninitialized ratelimit_state-&amp;amp;gt;lock access in __ext4_fill_super() kernel: netpoll: Fix race condition in netpoll_owner_active kernel: xfs: don&amp;amp;#39;t walk off the end of a directory data block kernel: xfs: add bounds checking to xlog_recover_process_data kernel: block: initialize integrity buffer to zero before writing it to media kernel: netfilt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:8617</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-54153</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54153</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 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: turn quotas off if mount failed after enabling quotas Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error value, the error handling path does not turn off the enabled quotas, which triggers the following kmemleak: ================================================================ unreferenced object 0xffff8cf68678e7c0 (size 64): comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s) hex dump (first 32 bytes): 00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A... c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H... backtrace: [&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880 [&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140 [&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0 [&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770 [&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0 [&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4] [&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4] [&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4] [&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370 [&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4] [&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160 [&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480 [&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0 [&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0 [&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160 [&amp;lt;0000000027d2140c…&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 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: turn quotas off if mount failed after enabling quotas Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error value, the error handling path does not turn off the enabled quotas, which triggers the following kmemleak: ================================================================ unreferenced object 0xffff8cf68678e7c0 (size 64): comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s) hex dump (first 32 bytes): 00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A... c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H... backtrace: [&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880 [&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140 [&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0 [&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770 [&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0 [&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4] [&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4] [&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4] [&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370 [&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4] [&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160 [&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480 [&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0 [&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0 [&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160 [&amp;lt;0000000027d2140c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54153</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</guid>
    </item>
  </channel>
</rss>
