<?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 00:53:32 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80644</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80644</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80644</guid>
    </item>
    <item>
      <title>EUVD-2026-361032</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361032</link>
      <description>EUVD-2026-361032</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361032</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80644</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80644</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ocfs2: don&amp;#39;t BUG_ON an invalid journal dinode&lt;/p&gt;
&lt;p&gt;[BUG]
A fuzzed OCFS2 image can corrupt the current slot journal dinode while
mount is still in progress. The mount path first reports the invalid
journal block and then crashes in shutdown:&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/ocfs2/journal.c:1034!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:ocfs2_journal_toggle_dirty+0x2d6/0x340 fs/ocfs2/journal.c:1034
Call Trace:
 ocfs2_journal_shutdown+0x414/0xc30 fs/ocfs2/journal.c:1116
 ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline]
 ocfs2_fill_super+0x30a9/0x3cd0 fs/ocfs2/super.c:1083
 get_tree_bdev_flags+0x38b/0x640 fs/super.c:1698
 get_tree_bdev+0x24/0x40 fs/super.c:1721
 ocfs2_get_tree+0x21/0x30 fs/ocfs2/super.c:1184
 vfs_get_tree+0x9a/0x370 fs/super.c:1758
 fc_mount fs/namespace.c:1199 [inline]
 do_new_mount_fc fs/namespace.c:3642 [inline]
 do_new_mount fs/namespace.c:3718 [inline]
 path_mount+0x5b8/0x1ea0 fs/namespace.c:4028
 do_mount fs/namespace.c:4041 [inline]
 __do_sys_mount fs/namespace.c:4229 [inline]
 __se_sys_mount fs/namespace.c:4206 [inline]
 __x64_sys_mount+0x282/0x320 fs/namespace.c:4206
 ...&lt;/p&gt;
&lt;p&gt;[CAUSE]
ocfs2_journal_toggle_dirty() used to return -EIO when journal-&amp;gt;j_bh no
longer contained a valid dinode, because the startup and shutdown paths
already handled that failure. Commit 10995aa2451a
(&amp;#34;ocfs2: Morph the haphazard OCFS2_IS_VALID_DINODE() checks.&amp;#34;) changed
the check to a BUG_ON() under the assumption th…&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;ocfs2: don&amp;#39;t BUG_ON an invalid journal dinode&lt;/p&gt;
&lt;p&gt;[BUG]
A fuzzed OCFS2 image can corrupt the current slot journal dinode while
mount is still in progress. The mount path first reports the invalid
journal block and then crashes in shutdown:&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/ocfs2/journal.c:1034!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:ocfs2_journal_toggle_dirty+0x2d6/0x340 fs/ocfs2/journal.c:1034
Call Trace:
 ocfs2_journal_shutdown+0x414/0xc30 fs/ocfs2/journal.c:1116
 ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline]
 ocfs2_fill_super+0x30a9/0x3cd0 fs/ocfs2/super.c:1083
 get_tree_bdev_flags+0x38b/0x640 fs/super.c:1698
 get_tree_bdev+0x24/0x40 fs/super.c:1721
 ocfs2_get_tree+0x21/0x30 fs/ocfs2/super.c:1184
 vfs_get_tree+0x9a/0x370 fs/super.c:1758
 fc_mount fs/namespace.c:1199 [inline]
 do_new_mount_fc fs/namespace.c:3642 [inline]
 do_new_mount fs/namespace.c:3718 [inline]
 path_mount+0x5b8/0x1ea0 fs/namespace.c:4028
 do_mount fs/namespace.c:4041 [inline]
 __do_sys_mount fs/namespace.c:4229 [inline]
 __se_sys_mount fs/namespace.c:4206 [inline]
 __x64_sys_mount+0x282/0x320 fs/namespace.c:4206
 ...&lt;/p&gt;
&lt;p&gt;[CAUSE]
ocfs2_journal_toggle_dirty() used to return -EIO when journal-&amp;gt;j_bh no
longer contained a valid dinode, because the startup and shutdown paths
already handled that failure. Commit 10995aa2451a
(&amp;#34;ocfs2: Morph the haphazard OCFS2_IS_VALID_DINODE() checks.&amp;#34;) changed
the check to a BUG_ON() under the assumption th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80644</guid>
    </item>
    <item>
      <title>GHSA-2fq5-fj4m-pqwr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2fq5-fj4m-pqwr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ocfs2: don&amp;#39;t BUG_ON an invalid journal dinode&lt;/p&gt;
&lt;p&gt;[BUG]
A fuzzed OCFS2 image can corrupt the current slot journal dinode while
mount is still in progress. The mount path first reports the invalid
journal block and then crashes in shutdown:&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/ocfs2/journal.c:1034!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:ocfs2_journal_toggle_dirty+0x2d6/0x340 fs/ocfs2/journal.c:1034
Call Trace:
 ocfs2_journal_shutdown+0x414/0xc30 fs/ocfs2/journal.c:1116
 ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline]
 ocfs2_fill_super+0x30a9/0x3cd0 fs/ocfs2/super.c:1083
 get_tree_bdev_flags+0x38b/0x640 fs/super.c:1698
 get_tree_bdev+0x24/0x40 fs/super.c:1721
 ocfs2_get_tree+0x21/0x30 fs/ocfs2/super.c:1184
 vfs_get_tree+0x9a/0x370 fs/super.c:1758
 fc_mount fs/namespace.c:1199 [inline]
 do_new_mount_fc fs/namespace.c:3642 [inline]
 do_new_mount fs/namespace.c:3718 [inline]
 path_mount+0x5b8/0x1ea0 fs/namespace.c:4028
 do_mount fs/namespace.c:4041 [inline]
 __do_sys_mount fs/namespace.c:4229 [inline]
 __se_sys_mount fs/namespace.c:4206 [inline]
 __x64_sys_mount+0x282/0x320 fs/namespace.c:4206
 ...&lt;/p&gt;
&lt;p&gt;[CAUSE]
ocfs2_journal_toggle_dirty() used to return -EIO when journal-&amp;gt;j_bh no
longer contained a valid dinode, because the startup and shutdown paths
already handled that failure. Commit 10995aa2451a
(&amp;#34;ocfs2: Morph the haphazard OCFS2_IS_VALID_DINODE() checks.&amp;#34;) changed
the check to a BUG_ON() under the assumption th…&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;ocfs2: don&amp;#39;t BUG_ON an invalid journal dinode&lt;/p&gt;
&lt;p&gt;[BUG]
A fuzzed OCFS2 image can corrupt the current slot journal dinode while
mount is still in progress. The mount path first reports the invalid
journal block and then crashes in shutdown:&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/ocfs2/journal.c:1034!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:ocfs2_journal_toggle_dirty+0x2d6/0x340 fs/ocfs2/journal.c:1034
Call Trace:
 ocfs2_journal_shutdown+0x414/0xc30 fs/ocfs2/journal.c:1116
 ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline]
 ocfs2_fill_super+0x30a9/0x3cd0 fs/ocfs2/super.c:1083
 get_tree_bdev_flags+0x38b/0x640 fs/super.c:1698
 get_tree_bdev+0x24/0x40 fs/super.c:1721
 ocfs2_get_tree+0x21/0x30 fs/ocfs2/super.c:1184
 vfs_get_tree+0x9a/0x370 fs/super.c:1758
 fc_mount fs/namespace.c:1199 [inline]
 do_new_mount_fc fs/namespace.c:3642 [inline]
 do_new_mount fs/namespace.c:3718 [inline]
 path_mount+0x5b8/0x1ea0 fs/namespace.c:4028
 do_mount fs/namespace.c:4041 [inline]
 __do_sys_mount fs/namespace.c:4229 [inline]
 __se_sys_mount fs/namespace.c:4206 [inline]
 __x64_sys_mount+0x282/0x320 fs/namespace.c:4206
 ...&lt;/p&gt;
&lt;p&gt;[CAUSE]
ocfs2_journal_toggle_dirty() used to return -EIO when journal-&amp;gt;j_bh no
longer contained a valid dinode, because the startup and shutdown paths
already handled that failure. Commit 10995aa2451a
(&amp;#34;ocfs2: Morph the haphazard OCFS2_IS_VALID_DINODE() checks.&amp;#34;) changed
the check to a BUG_ON() under the assumption th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2fq5-fj4m-pqwr</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80644</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80644</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ocfs2: don&amp;#39;t BUG_ON an invalid journal dinode [BUG] A fuzzed OCFS2 image can corrupt the current slot journal dinode while mount is still in progress. The mount path first reports the invalid journal block and then crashes in shutdown: kernel BUG at fs/ocfs2/journal.c:1034! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:ocfs2_journal_toggle_dirty+0x2d6/0x340 fs/ocfs2/journal.c:1034 Call Trace:  ocfs2_journal_shutdown+0x414/0xc30 fs/ocfs2/journal.c:1116  ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline]  ocfs2_fill_super+0x30a9/0x3cd0 fs/ocfs2/super.c:1083  get_tree_bdev_flags+0x38b/0x640 fs/super.c:1698  get_tree_bdev+0x24/0x40 fs/super.c:1721  ocfs2_get_tree+0x21/0x30 fs/ocfs2/super.c:1184  vfs_get_tree+0x9a/0x370 fs/super.c:1758  fc_mount fs/namespace.c:1199 [inline]  do_new_mount_fc fs/namespace.c:3642 [inline]  do_new_mount fs/namespace.c:3718 [inline]  path_mount+0x5b8/0x1ea0 fs/namespace.c:4028  do_mount fs/namespace.c:4041 [inline]  __do_sys_mount fs/namespace.c:4229 [inline]  __se_sys_mount fs/namespace.c:4206 [inline]  __x64_sys_mount+0x282/0x320 fs/namespace.c:4206  ... [CAUSE] ocfs2_journal_toggle_dirty() used to return -EIO when journal-&amp;gt;j_bh no longer contained a valid dinode, because the startup and shutdown paths already handled that failure. Commit 10995aa2451a (&amp;#34;ocfs2: Morph the haphazard OCFS2_IS_VALID_DINODE() checks.&amp;#34;) changed the check to a BUG_ON() under the assumption that t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ocfs2: don&amp;#39;t BUG_ON an invalid journal dinode [BUG] A fuzzed OCFS2 image can corrupt the current slot journal dinode while mount is still in progress. The mount path first reports the invalid journal block and then crashes in shutdown: kernel BUG at fs/ocfs2/journal.c:1034! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:ocfs2_journal_toggle_dirty+0x2d6/0x340 fs/ocfs2/journal.c:1034 Call Trace:  ocfs2_journal_shutdown+0x414/0xc30 fs/ocfs2/journal.c:1116  ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline]  ocfs2_fill_super+0x30a9/0x3cd0 fs/ocfs2/super.c:1083  get_tree_bdev_flags+0x38b/0x640 fs/super.c:1698  get_tree_bdev+0x24/0x40 fs/super.c:1721  ocfs2_get_tree+0x21/0x30 fs/ocfs2/super.c:1184  vfs_get_tree+0x9a/0x370 fs/super.c:1758  fc_mount fs/namespace.c:1199 [inline]  do_new_mount_fc fs/namespace.c:3642 [inline]  do_new_mount fs/namespace.c:3718 [inline]  path_mount+0x5b8/0x1ea0 fs/namespace.c:4028  do_mount fs/namespace.c:4041 [inline]  __do_sys_mount fs/namespace.c:4229 [inline]  __se_sys_mount fs/namespace.c:4206 [inline]  __x64_sys_mount+0x282/0x320 fs/namespace.c:4206  ... [CAUSE] ocfs2_journal_toggle_dirty() used to return -EIO when journal-&amp;gt;j_bh no longer contained a valid dinode, because the startup and shutdown paths already handled that failure. Commit 10995aa2451a (&amp;#34;ocfs2: Morph the haphazard OCFS2_IS_VALID_DINODE() checks.&amp;#34;) changed the check to a BUG_ON() under the assumption that t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80644</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&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, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
