<?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 05:04:23 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-08385</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-08385</link>
      <description>bdu:2024-08385</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-08385</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0578 — 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-0578</link>
      <description>certfr-2024-avi-0578</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578</guid>
    </item>
    <item>
      <title>EUVD-2026-309536</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309536</link>
      <description>EUVD-2026-309536</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309536</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47089</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47089</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;kfence: fix memory leak when cat kfence objects&lt;/p&gt;
&lt;p&gt;Hulk robot reported a kmemleak problem:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff93d1d8cc02e8 (size 248):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        00 40 85 19 d4 93 ff ff 00 10 00 00 00 00 00 00  .@..............
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
         seq_open+0x2a/0x80
         full_proxy_open+0x167/0x1e0
         do_dentry_open+0x1e1/0x3a0
         path_openat+0x961/0xa20
         do_filp_open+0xae/0x120
         do_sys_openat2+0x216/0x2f0
         do_sys_open+0x57/0x80
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9
    unreferenced object 0xffff93d419854000 (size 4096):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        6b 66 65 6e 63 65 2d 23 32 35 30 3a 20 30 78 30  kfence-#250: 0x0
        30 30 30 30 30 30 30 37 35 34 62 64 61 31 32 2d  0000000754bda12-
      backtrace:
         seq_read_iter+0x313/0x440
         seq_read+0x14b/0x1a0
         full_proxy_read+0x56/0x80
         vfs_read+0xa5/0x1b0
         ksys_read+0xa0/0xf0
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9&lt;/p&gt;
&lt;p&gt;I find that we can easily reproduce this problem with the following
commands:&lt;/p&gt;
&lt;p&gt;cat /sys/kernel/debug/kfence/objects
	echo scan &amp;gt; /sys/kernel/…&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;kfence: fix memory leak when cat kfence objects&lt;/p&gt;
&lt;p&gt;Hulk robot reported a kmemleak problem:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff93d1d8cc02e8 (size 248):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        00 40 85 19 d4 93 ff ff 00 10 00 00 00 00 00 00  .@..............
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
         seq_open+0x2a/0x80
         full_proxy_open+0x167/0x1e0
         do_dentry_open+0x1e1/0x3a0
         path_openat+0x961/0xa20
         do_filp_open+0xae/0x120
         do_sys_openat2+0x216/0x2f0
         do_sys_open+0x57/0x80
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9
    unreferenced object 0xffff93d419854000 (size 4096):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        6b 66 65 6e 63 65 2d 23 32 35 30 3a 20 30 78 30  kfence-#250: 0x0
        30 30 30 30 30 30 30 37 35 34 62 64 61 31 32 2d  0000000754bda12-
      backtrace:
         seq_read_iter+0x313/0x440
         seq_read+0x14b/0x1a0
         full_proxy_read+0x56/0x80
         vfs_read+0xa5/0x1b0
         ksys_read+0xa0/0xf0
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9&lt;/p&gt;
&lt;p&gt;I find that we can easily reproduce this problem with the following
commands:&lt;/p&gt;
&lt;p&gt;cat /sys/kernel/debug/kfence/objects
	echo scan &amp;gt; /sys/kernel/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47089</guid>
    </item>
    <item>
      <title>GHSA-97gj-q9fx-vc88</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-97gj-q9fx-vc88</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;kfence: fix memory leak when cat kfence objects&lt;/p&gt;
&lt;p&gt;Hulk robot reported a kmemleak problem:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff93d1d8cc02e8 (size 248):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        00 40 85 19 d4 93 ff ff 00 10 00 00 00 00 00 00  .@..............
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
         seq_open+0x2a/0x80
         full_proxy_open+0x167/0x1e0
         do_dentry_open+0x1e1/0x3a0
         path_openat+0x961/0xa20
         do_filp_open+0xae/0x120
         do_sys_openat2+0x216/0x2f0
         do_sys_open+0x57/0x80
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9
    unreferenced object 0xffff93d419854000 (size 4096):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        6b 66 65 6e 63 65 2d 23 32 35 30 3a 20 30 78 30  kfence-#250: 0x0
        30 30 30 30 30 30 30 37 35 34 62 64 61 31 32 2d  0000000754bda12-
      backtrace:
         seq_read_iter+0x313/0x440
         seq_read+0x14b/0x1a0
         full_proxy_read+0x56/0x80
         vfs_read+0xa5/0x1b0
         ksys_read+0xa0/0xf0
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9&lt;/p&gt;
&lt;p&gt;I find that we can easily reproduce this problem with the following
commands:&lt;/p&gt;
&lt;p&gt;cat /sys/kernel/debug/kfence/objects
	echo scan &amp;gt; /sys/kernel/…&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;kfence: fix memory leak when cat kfence objects&lt;/p&gt;
&lt;p&gt;Hulk robot reported a kmemleak problem:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff93d1d8cc02e8 (size 248):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        00 40 85 19 d4 93 ff ff 00 10 00 00 00 00 00 00  .@..............
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
         seq_open+0x2a/0x80
         full_proxy_open+0x167/0x1e0
         do_dentry_open+0x1e1/0x3a0
         path_openat+0x961/0xa20
         do_filp_open+0xae/0x120
         do_sys_openat2+0x216/0x2f0
         do_sys_open+0x57/0x80
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9
    unreferenced object 0xffff93d419854000 (size 4096):
      comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)
      hex dump (first 32 bytes):
        6b 66 65 6e 63 65 2d 23 32 35 30 3a 20 30 78 30  kfence-#250: 0x0
        30 30 30 30 30 30 30 37 35 34 62 64 61 31 32 2d  0000000754bda12-
      backtrace:
         seq_read_iter+0x313/0x440
         seq_read+0x14b/0x1a0
         full_proxy_read+0x56/0x80
         vfs_read+0xa5/0x1b0
         ksys_read+0xa0/0xf0
         do_syscall_64+0x33/0x40
         entry_SYSCALL_64_after_hwframe+0x44/0xa9&lt;/p&gt;
&lt;p&gt;I find that we can easily reproduce this problem with the following
commands:&lt;/p&gt;
&lt;p&gt;cat /sys/kernel/debug/kfence/objects
	echo scan &amp;gt; /sys/kernel/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-97gj-q9fx-vc88</guid>
    </item>
    <item>
      <title>gsd-2021-47089</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47089</link>
      <description>gsd-2021-47089</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47089</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2372-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2372-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:2372-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47089</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47089</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kfence: fix memory leak when cat kfence objects Hulk robot reported a kmemleak problem:     unreferenced object 0xffff93d1d8cc02e8 (size 248):       comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)       hex dump (first 32 bytes):         00 40 85 19 d4 93 ff ff 00 10 00 00 00 00 00 00  .@..............         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................       backtrace:          seq_open+0x2a/0x80          full_proxy_open+0x167/0x1e0          do_dentry_open+0x1e1/0x3a0          path_openat+0x961/0xa20          do_filp_open+0xae/0x120          do_sys_openat2+0x216/0x2f0          do_sys_open+0x57/0x80          do_syscall_64+0x33/0x40          entry_SYSCALL_64_after_hwframe+0x44/0xa9     unreferenced object 0xffff93d419854000 (size 4096):       comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)       hex dump (first 32 bytes):         6b 66 65 6e 63 65 2d 23 32 35 30 3a 20 30 78 30  kfence-#250: 0x0         30 30 30 30 30 30 30 37 35 34 62 64 61 31 32 2d  0000000754bda12-       backtrace:          seq_read_iter+0x313/0x440          seq_read+0x14b/0x1a0          full_proxy_read+0x56/0x80          vfs_read+0xa5/0x1b0          ksys_read+0xa0/0xf0          do_syscall_64+0x33/0x40          entry_SYSCALL_64_after_hwframe+0x44/0xa9 I find that we can easily reproduce this problem with the following commands: 	cat /sys/kernel/debug/kfence/objects 	echo scan &amp;gt; /sys/kernel/debug…&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kfence: fix memory leak when cat kfence objects Hulk robot reported a kmemleak problem:     unreferenced object 0xffff93d1d8cc02e8 (size 248):       comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)       hex dump (first 32 bytes):         00 40 85 19 d4 93 ff ff 00 10 00 00 00 00 00 00  .@..............         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................       backtrace:          seq_open+0x2a/0x80          full_proxy_open+0x167/0x1e0          do_dentry_open+0x1e1/0x3a0          path_openat+0x961/0xa20          do_filp_open+0xae/0x120          do_sys_openat2+0x216/0x2f0          do_sys_open+0x57/0x80          do_syscall_64+0x33/0x40          entry_SYSCALL_64_after_hwframe+0x44/0xa9     unreferenced object 0xffff93d419854000 (size 4096):       comm &amp;#34;cat&amp;#34;, pid 23327, jiffies 4624670141 (age 495992.217s)       hex dump (first 32 bytes):         6b 66 65 6e 63 65 2d 23 32 35 30 3a 20 30 78 30  kfence-#250: 0x0         30 30 30 30 30 30 30 37 35 34 62 64 61 31 32 2d  0000000754bda12-       backtrace:          seq_read_iter+0x313/0x440          seq_read+0x14b/0x1a0          full_proxy_read+0x56/0x80          vfs_read+0xa5/0x1b0          ksys_read+0xa0/0xf0          do_syscall_64+0x33/0x40          entry_SYSCALL_64_after_hwframe+0x44/0xa9 I find that we can easily reproduce this problem with the following commands: 	cat /sys/kernel/debug/kfence/objects 	echo scan &amp;gt; /sys/kernel/debug…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47089</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0549 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0549</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel 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 mehrere Schwachstellen im Linux-Kernel 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-0549</guid>
    </item>
  </channel>
</rss>
