<?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://vulnerability.circl.lu</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, 30 Sep 2026 10:00:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72368 — cachefiles: Fix double unlock in nomem_d_alloc error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72368</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;cachefiles: Fix double unlock in nomem_d_alloc error path&lt;/p&gt;
&lt;p&gt;When start_creating() fails and returns -ENOMEM, it has already
released the parent directory lock in __start_dirop():&lt;/p&gt;
&lt;p&gt;static struct dentry *__start_dirop(...)
    {
        ...
        inode_lock_nested(dir, I_MUTEX_PARENT);
        dentry = lookup_one_qstr_excl(name, parent, lookup_flags);
        if (IS_ERR(dentry))
            inode_unlock(dir);  &amp;lt;-- Lock released on error
        return dentry;
    }&lt;/p&gt;
&lt;p&gt;However, the nomem_d_alloc error path in cachefiles_get_directory()
unconditionally calls inode_unlock(d_inode(dir)) again, causing a
double unlock that corrupts the rwsem state.&lt;/p&gt;
&lt;p&gt;This is a leftover from commit 7ab96df840e60 which replaced manual
locking with start_creating() but failed to update the nomem_d_alloc
path (while correctly updating mkdir_error and lookup_error paths).&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;cachefiles: Fix double unlock in nomem_d_alloc error path&lt;/p&gt;
&lt;p&gt;When start_creating() fails and returns -ENOMEM, it has already
released the parent directory lock in __start_dirop():&lt;/p&gt;
&lt;p&gt;static struct dentry *__start_dirop(...)
    {
        ...
        inode_lock_nested(dir, I_MUTEX_PARENT);
        dentry = lookup_one_qstr_excl(name, parent, lookup_flags);
        if (IS_ERR(dentry))
            inode_unlock(dir);  &amp;lt;-- Lock released on error
        return dentry;
    }&lt;/p&gt;
&lt;p&gt;However, the nomem_d_alloc error path in cachefiles_get_directory()
unconditionally calls inode_unlock(d_inode(dir)) again, causing a
double unlock that corrupts the rwsem state.&lt;/p&gt;
&lt;p&gt;This is a leftover from commit 7ab96df840e60 which replaced manual
locking with start_creating() but failed to update the nomem_d_alloc
path (while correctly updating mkdir_error and lookup_error paths).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72368</guid>
    </item>
  </channel>
</rss>
