<?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-05T16:39:41.991203+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-37856</id>
    <title>CVE-2025-37856 — btrfs: harden block_group::bg_list against list_del() races</title>
    <updated>2026-10-05T16:39:41.994183+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: harden block_group::bg_list against list_del() races</p>
<p>As far as I can tell, these calls of list_del_init() on bg_list cannot
run concurrently with btrfs_mark_bg_unused() or btrfs_mark_bg_to_reclaim(),
as they are in transaction error paths and situations where the block
group is readonly.</p>
<p>However, if there is any chance at all of racing with mark_bg_unused(),
or a different future user of bg_list, better to be safe than sorry.</p>
<p>Otherwise we risk the following interleaving (bg_list refcount in parens)</p>
<p>T1 (some random op)                       T2 (btrfs_mark_bg_unused)
                                        !list_empty(&amp;bg-&gt;bg_list); (1)
list_del_init(&amp;bg-&gt;bg_list); (1)
                                        list_move_tail (1)
btrfs_put_block_group (0)
                                        btrfs_delete_unused_bgs
                                             bg = list_first_entry
                                             list_del_init(&amp;bg-&gt;bg_list);
                                             btrfs_put_block_group(bg); (-1)</p>
<p>Ultimately, this results in a broken ref count that hits zero one deref
early and the real final deref underflows the refcount, resulting in a WARNING.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-37856"/>
  </entry>
</feed>
