<?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://db.gcve.eu</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>Thu, 12 Nov 2026 06:18:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98445 — xfs: don't let memory failures leak blocks and kill repairs</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98445</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: don&amp;#39;t let memory failures leak blocks and kill repairs&lt;/p&gt;
&lt;p&gt;LOLLM complains that a memory allocation failure in
xrep_newbt_add_blocks results in online repair leaking blocks that were
previously allocated to write a new btree, but the problem is worse than
that -- a limitation of the codebase is that the callers cannot undo the
transaction /and/ return the error -- either you undo all changes and
commit the transaction, or you error out and the filesystem goes down.&lt;/p&gt;
&lt;p&gt;However, the new btree space reservation object isn&amp;#39;t that big (~48
bytes).  Let&amp;#39;s just do a NOFAIL allocation and the problem goes away.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: don&amp;#39;t let memory failures leak blocks and kill repairs&lt;/p&gt;
&lt;p&gt;LOLLM complains that a memory allocation failure in
xrep_newbt_add_blocks results in online repair leaking blocks that were
previously allocated to write a new btree, but the problem is worse than
that -- a limitation of the codebase is that the callers cannot undo the
transaction /and/ return the error -- either you undo all changes and
commit the transaction, or you error out and the filesystem goes down.&lt;/p&gt;
&lt;p&gt;However, the new btree space reservation object isn&amp;#39;t that big (~48
bytes).  Let&amp;#39;s just do a NOFAIL allocation and the problem goes away.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98445</guid>
    </item>
  </channel>
</rss>
