<?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-09-30T03:09:31.466394+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-71159</id>
    <title>CVE-2025-71159 — btrfs: fix use-after-free warning in btrfs_get_or_create_delayed_node()</title>
    <updated>2026-09-30T03:09:31.841652+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 use-after-free warning in btrfs_get_or_create_delayed_node()</p>
<p>Previously, btrfs_get_or_create_delayed_node() set the delayed_node's
refcount before acquiring the root-&gt;delayed_nodes lock.
Commit e8513c012de7 ("btrfs: implement ref_tracker for delayed_nodes")
moved refcount_set inside the critical section, which means there is
no longer a memory barrier between setting the refcount and setting
btrfs_inode-&gt;delayed_node.</p>
<p>Without that barrier, the stores to node-&gt;refs and
btrfs_inode-&gt;delayed_node may become visible out of order. Another
thread can then read btrfs_inode-&gt;delayed_node and attempt to
increment a refcount that hasn't been set yet, leading to a
refcounting bug and a use-after-free warning.</p>
<p>The fix is to move refcount_set back to where it was to take
advantage of the implicit memory barrier provided by lock
acquisition.</p>
<p>Because the allocations now happen outside of the lock's critical
section, they can use GFP_NOFS instead of GFP_ATOMIC.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-71159"/>
  </entry>
</feed>
