<?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>Mon, 28 Sep 2026 18:39:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31666 — btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31666</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: fix incorrect return value after changing leaf in lookup_extent_data_ref()&lt;/p&gt;
&lt;p&gt;After commit 1618aa3c2e01 (&amp;#34;btrfs: simplify return variables in
lookup_extent_data_ref()&amp;#34;), the err and ret variables were merged into
a single ret variable. However, when btrfs_next_leaf() returns 0
(success), ret is overwritten from -ENOENT to 0. If the first key in
the next leaf does not match (different objectid or type), the function
returns 0 instead of -ENOENT, making the caller believe the lookup
succeeded when it did not. This can lead to operations on the wrong
extent tree item, potentially causing extent tree corruption.&lt;/p&gt;
&lt;p&gt;Fix this by returning -ENOENT directly when the key does not match,
instead of relying on the ret variable.&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: fix incorrect return value after changing leaf in lookup_extent_data_ref()&lt;/p&gt;
&lt;p&gt;After commit 1618aa3c2e01 (&amp;#34;btrfs: simplify return variables in
lookup_extent_data_ref()&amp;#34;), the err and ret variables were merged into
a single ret variable. However, when btrfs_next_leaf() returns 0
(success), ret is overwritten from -ENOENT to 0. If the first key in
the next leaf does not match (different objectid or type), the function
returns 0 instead of -ENOENT, making the caller believe the lookup
succeeded when it did not. This can lead to operations on the wrong
extent tree item, potentially causing extent tree corruption.&lt;/p&gt;
&lt;p&gt;Fix this by returning -ENOENT directly when the key does not match,
instead of relying on the ret variable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31666</guid>
    </item>
  </channel>
</rss>
