<?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-29T03:51:56.654277+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-2024-27058</id>
    <title>CVE-2024-27058 — tmpfs: fix race on handling dquot rbtree</title>
    <updated>2026-09-29T03:51:56.672257+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>tmpfs: fix race on handling dquot rbtree</p>
<p>A syzkaller reproducer found a race while attempting to remove dquot
information from the rb tree.</p>
<p>Fetching the rb_tree root node must also be protected by the
dqopt-&gt;dqio_sem, otherwise, giving the right timing, shmem_release_dquot()
will trigger a warning because it couldn't find a node in the tree, when
the real reason was the root node changing before the search starts:</p>
<p>Thread 1				Thread 2
- shmem_release_dquot()			- shmem_{acquire,release}_dquot()</p>
<p>- fetch ROOT				- Fetch ROOT</p>
<p>- acquire dqio_sem
- wait dqio_sem</p>
<p>- do something, triger a tree rebalance
					- release dqio_sem</p>
<p>- acquire dqio_sem
- start searching for the node, but
  from the wrong location, missing
  the node, and triggering a warning.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-27058"/>
  </entry>
</feed>
