<?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>Thu, 01 Oct 2026 13:55:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38243 — btrfs: fix invalid inode pointer dereferences during log replay</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38243</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 invalid inode pointer dereferences during log replay&lt;/p&gt;
&lt;p&gt;In a few places where we call read_one_inode(), if we get a NULL pointer
we end up jumping into an error path, or fallthrough in case of
__add_inode_ref(), where we then do something like this:&lt;/p&gt;
&lt;p&gt;iput(&amp;amp;inode-&amp;gt;vfs_inode);&lt;/p&gt;
&lt;p&gt;which results in an invalid inode pointer that triggers an invalid memory
access, resulting in a crash.&lt;/p&gt;
&lt;p&gt;Fix this by making sure we don&amp;#39;t do such dereferences.&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 invalid inode pointer dereferences during log replay&lt;/p&gt;
&lt;p&gt;In a few places where we call read_one_inode(), if we get a NULL pointer
we end up jumping into an error path, or fallthrough in case of
__add_inode_ref(), where we then do something like this:&lt;/p&gt;
&lt;p&gt;iput(&amp;amp;inode-&amp;gt;vfs_inode);&lt;/p&gt;
&lt;p&gt;which results in an invalid inode pointer that triggers an invalid memory
access, resulting in a crash.&lt;/p&gt;
&lt;p&gt;Fix this by making sure we don&amp;#39;t do such dereferences.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38243</guid>
    </item>
  </channel>
</rss>
