<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 04:35:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23423 — btrfs: free pages on error in btrfs_uring_read_extent()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23423</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;btrfs: free pages on error in btrfs_uring_read_extent()&lt;/p&gt;
&lt;p&gt;In this function the &amp;#39;pages&amp;#39; object is never freed in the hopes that it is
picked up by btrfs_uring_read_finished() whenever that executes in the
future. But that&amp;#39;s just the happy path. Along the way previous
allocations might have gone wrong, or we might not get -EIOCBQUEUED from
btrfs_encoded_read_regular_fill_pages(). In all these cases, we go to a
cleanup section that frees all memory allocated by this function without
assuming any deferred execution, and this also needs to happen for the
&amp;#39;pages&amp;#39; allocation.&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;btrfs: free pages on error in btrfs_uring_read_extent()&lt;/p&gt;
&lt;p&gt;In this function the &amp;#39;pages&amp;#39; object is never freed in the hopes that it is
picked up by btrfs_uring_read_finished() whenever that executes in the
future. But that&amp;#39;s just the happy path. Along the way previous
allocations might have gone wrong, or we might not get -EIOCBQUEUED from
btrfs_encoded_read_regular_fill_pages(). In all these cases, we go to a
cleanup section that frees all memory allocated by this function without
assuming any deferred execution, and this also needs to happen for the
&amp;#39;pages&amp;#39; allocation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23423</guid>
    </item>
  </channel>
</rss>
