<?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-04T05:48:47.950407+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-2022-50379</id>
    <title>CVE-2022-50379 — btrfs: fix race between quota enable and quota rescan ioctl</title>
    <updated>2026-10-04T05:48:47.969353+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 race between quota enable and quota rescan ioctl</p>
<p>When enabling quotas, at btrfs_quota_enable(), after committing the
transaction, we change fs_info-&gt;quota_root to point to the quota root we
created and set BTRFS_FS_QUOTA_ENABLED at fs_info-&gt;flags. Then we try
to start the qgroup rescan worker, first by initializing it with a call
to qgroup_rescan_init() - however if that fails we end up freeing the
quota root but we leave fs_info-&gt;quota_root still pointing to it, this
can later result in a use-after-free somewhere else.</p>
<p>We have previously set the flags BTRFS_FS_QUOTA_ENABLED and
BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at
btrfs_quota_enable(), which is possible if someone already called the
quota rescan ioctl, and therefore started the rescan worker.</p>
<p>So fix this by ignoring an -EINPROGRESS and asserting we can't get any
other error.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50379"/>
  </entry>
</feed>
