<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T13:55:19.716747+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-38243</id>
    <title>CVE-2025-38243 — btrfs: fix invalid inode pointer dereferences during log replay</title>
    <updated>2026-10-01T13:55:19.718903+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>btrfs: fix invalid inode pointer dereferences during log replay</p>
<p>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:</p>
<p>iput(&amp;inode-&gt;vfs_inode);</p>
<p>which results in an invalid inode pointer that triggers an invalid memory
access, resulting in a crash.</p>
<p>Fix this by making sure we don't do such dereferences.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38243"/>
  </entry>
</feed>
