<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 05:43:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49761 — btrfs: always report error in run_one_delayed_ref()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49761</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: always report error in run_one_delayed_ref()&lt;/p&gt;
&lt;p&gt;Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but
if end users hit such problem, there will be no chance that
btrfs_debug() is enabled.  This can lead to very little useful info for
debugging.&lt;/p&gt;
&lt;p&gt;This patch will:&lt;/p&gt;
&lt;p&gt;- Add extra info for error reporting
  Including:
  * logical bytenr
  * num_bytes
  * type
  * action
  * ref_mod&lt;/p&gt;
&lt;p&gt;- Replace the btrfs_debug() with btrfs_err()&lt;/p&gt;
&lt;p&gt;- Move the error reporting into run_one_delayed_ref()
  This is to avoid use-after-free, the @node can be freed in the caller.&lt;/p&gt;
&lt;p&gt;This error should only be triggered at most once.&lt;/p&gt;
&lt;p&gt;As if run_one_delayed_ref() failed, we trigger the error message, then
causing the call chain to error out:&lt;/p&gt;
&lt;p&gt;btrfs_run_delayed_refs()
`- btrfs_run_delayed_refs()
   `- btrfs_run_delayed_refs_for_head()
      `- run_one_delayed_ref()&lt;/p&gt;
&lt;p&gt;And we will abort the current transaction in btrfs_run_delayed_refs().
If we have to run delayed refs for the abort transaction,
run_one_delayed_ref() will just cleanup the refs and do nothing, thus no
new error messages would be output.&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: always report error in run_one_delayed_ref()&lt;/p&gt;
&lt;p&gt;Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but
if end users hit such problem, there will be no chance that
btrfs_debug() is enabled.  This can lead to very little useful info for
debugging.&lt;/p&gt;
&lt;p&gt;This patch will:&lt;/p&gt;
&lt;p&gt;- Add extra info for error reporting
  Including:
  * logical bytenr
  * num_bytes
  * type
  * action
  * ref_mod&lt;/p&gt;
&lt;p&gt;- Replace the btrfs_debug() with btrfs_err()&lt;/p&gt;
&lt;p&gt;- Move the error reporting into run_one_delayed_ref()
  This is to avoid use-after-free, the @node can be freed in the caller.&lt;/p&gt;
&lt;p&gt;This error should only be triggered at most once.&lt;/p&gt;
&lt;p&gt;As if run_one_delayed_ref() failed, we trigger the error message, then
causing the call chain to error out:&lt;/p&gt;
&lt;p&gt;btrfs_run_delayed_refs()
`- btrfs_run_delayed_refs()
   `- btrfs_run_delayed_refs_for_head()
      `- run_one_delayed_ref()&lt;/p&gt;
&lt;p&gt;And we will abort the current transaction in btrfs_run_delayed_refs().
If we have to run delayed refs for the abort transaction,
run_one_delayed_ref() will just cleanup the refs and do nothing, thus no
new error messages would be output.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49761</guid>
    </item>
  </channel>
</rss>
