<?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 16:57:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71184 — btrfs: fix NULL dereference on root when tracing inode eviction</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71184</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 NULL dereference on root when tracing inode eviction&lt;/p&gt;
&lt;p&gt;When evicting an inode the first thing we do is to setup tracing for it,
which implies fetching the root&amp;#39;s id. But in btrfs_evict_inode() the
root might be NULL, as implied in the next check that we do in
btrfs_evict_inode().&lt;/p&gt;
&lt;p&gt;Hence, we either should set the -&amp;gt;root_objectid to 0 in case the root is
NULL, or we move tracing setup after checking that the root is not
NULL. Setting the rootid to 0 at least gives us the possibility to trace
this call even in the case when the root is NULL, so that&amp;#39;s the solution
taken here.&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 NULL dereference on root when tracing inode eviction&lt;/p&gt;
&lt;p&gt;When evicting an inode the first thing we do is to setup tracing for it,
which implies fetching the root&amp;#39;s id. But in btrfs_evict_inode() the
root might be NULL, as implied in the next check that we do in
btrfs_evict_inode().&lt;/p&gt;
&lt;p&gt;Hence, we either should set the -&amp;gt;root_objectid to 0 in case the root is
NULL, or we move tracing setup after checking that the root is not
NULL. Setting the rootid to 0 at least gives us the possibility to trace
this call even in the case when the root is NULL, so that&amp;#39;s the solution
taken here.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71184</guid>
    </item>
  </channel>
</rss>
