<?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://127.0.0.1:10001</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, 21 Nov 2026 09:45:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-55641</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-55641</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://127.0.0.1:10001/vuln/bell-cve-2024-55641</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0254 — 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://127.0.0.1:10001/vuln/certfr-2025-avi-0254</link>
      <description>certfr-2025-avi-0254</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0254</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-55641</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-55641</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 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: unlock inodes when erroring out of xfs_trans_alloc_dir Debugging a filesystem patch with generic/475 caused the system to hang after observing the following sequences in dmesg:  XFS (dm-0): metadata I/O error in &amp;#34;xfs_imap_to_bp+0x61/0xe0 [xfs]&amp;#34; at daddr 0x491520 len 32 error 5  XFS (dm-0): metadata I/O error in &amp;#34;xfs_btree_read_buf_block+0xba/0x160 [xfs]&amp;#34; at daddr 0x3445608 len 8 error 5  XFS (dm-0): metadata I/O error in &amp;#34;xfs_imap_to_bp+0x61/0xe0 [xfs]&amp;#34; at daddr 0x138e1c0 len 32 error 5  XFS (dm-0): log I/O error -5  XFS (dm-0): Metadata I/O Error (0x1) detected at xfs_trans_read_buf_map+0x1ea/0x4b0 [xfs] (fs/xfs/xfs_trans_buf.c:311). Shutting down filesystem.  XFS (dm-0): Please unmount the filesystem and rectify the problem(s)  XFS (dm-0): Internal error dqp-&amp;gt;q_ino.reserved &amp;lt; dqp-&amp;gt;q_ino.count at line 869 of file fs/xfs/xfs_trans_dquot.c.  Caller xfs_trans_dqresv+0x236/0x440 [xfs]  XFS (dm-0): Corruption detected. Unmount and run xfs_repair  XFS (dm-0): Unmounting Filesystem be6bcbcc-9921-4deb-8d16-7cc94e335fa7 The system is stuck in unmount trying to lock a couple of inodes so that they can be purged.  The dquot corruption notice above is a clue to what happened -- a link() call tried to set up a transaction to link a child into a directory.  Quota reservation for the transaction failed after IO errors shut down the filesystem, but then we forgot to unlock the inodes on our way out.  Fix that.&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 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: unlock inodes when erroring out of xfs_trans_alloc_dir Debugging a filesystem patch with generic/475 caused the system to hang after observing the following sequences in dmesg:  XFS (dm-0): metadata I/O error in &amp;#34;xfs_imap_to_bp+0x61/0xe0 [xfs]&amp;#34; at daddr 0x491520 len 32 error 5  XFS (dm-0): metadata I/O error in &amp;#34;xfs_btree_read_buf_block+0xba/0x160 [xfs]&amp;#34; at daddr 0x3445608 len 8 error 5  XFS (dm-0): metadata I/O error in &amp;#34;xfs_imap_to_bp+0x61/0xe0 [xfs]&amp;#34; at daddr 0x138e1c0 len 32 error 5  XFS (dm-0): log I/O error -5  XFS (dm-0): Metadata I/O Error (0x1) detected at xfs_trans_read_buf_map+0x1ea/0x4b0 [xfs] (fs/xfs/xfs_trans_buf.c:311). Shutting down filesystem.  XFS (dm-0): Please unmount the filesystem and rectify the problem(s)  XFS (dm-0): Internal error dqp-&amp;gt;q_ino.reserved &amp;lt; dqp-&amp;gt;q_ino.count at line 869 of file fs/xfs/xfs_trans_dquot.c.  Caller xfs_trans_dqresv+0x236/0x440 [xfs]  XFS (dm-0): Corruption detected. Unmount and run xfs_repair  XFS (dm-0): Unmounting Filesystem be6bcbcc-9921-4deb-8d16-7cc94e335fa7 The system is stuck in unmount trying to lock a couple of inodes so that they can be purged.  The dquot corruption notice above is a clue to what happened -- a link() call tried to set up a transaction to link a child into a directory.  Quota reservation for the transaction failed after IO errors shut down the filesystem, but then we forgot to unlock the inodes on our way out.  Fix that.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-55641</guid>
    </item>
  </channel>
</rss>
