<?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>Thu, 01 Oct 2026 19:53:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68096 — audit: fix recursive locking deadlock in audit_dupe_exe()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68096</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;audit: fix recursive locking deadlock in audit_dupe_exe()&lt;/p&gt;
&lt;p&gt;A deadlock occurs in the audit subsystem when duplicating
executable-related rules.&lt;/p&gt;
&lt;p&gt;When a file is moved (e.g., via do_renameat2()), the VFS layer locks
the parent directory (I_MUTEX_PARENT), which synchronously triggers an
fsnotify_move event. If an existing executable audit rule matches the
file being moved, the audit subsystem catches this event and calls
audit_dupe_exe() to duplicate the watch and update the rule. Then,
audit_alloc_mark() would call kern_path_parent() to resolve the path,
leading to a blind attempt to acquire the exact same I_MUTEX_PARENT lock
already held by the task, resulting in the following recursive locking
deadlock:&lt;/p&gt;
&lt;p&gt;============================================
 WARNING: possible recursive locking detected
 6.12.0-55.27.1.el10_0.x86_64+debug #1 Not tainted
 --------------------------------------------
 mv/5099 is trying to acquire lock:
 ffff888132845358 (&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1){+.+.}-{3:3},
 at: __kern_path_locked+0x10a/0x2f0&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
 ffff888132846b58 (&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1){+.+.}-{3:3},
 at: lock_two_directories+0x13f/0x2b0&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
  Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
        ----
   lock(&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1);
   lock(&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be…&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;audit: fix recursive locking deadlock in audit_dupe_exe()&lt;/p&gt;
&lt;p&gt;A deadlock occurs in the audit subsystem when duplicating
executable-related rules.&lt;/p&gt;
&lt;p&gt;When a file is moved (e.g., via do_renameat2()), the VFS layer locks
the parent directory (I_MUTEX_PARENT), which synchronously triggers an
fsnotify_move event. If an existing executable audit rule matches the
file being moved, the audit subsystem catches this event and calls
audit_dupe_exe() to duplicate the watch and update the rule. Then,
audit_alloc_mark() would call kern_path_parent() to resolve the path,
leading to a blind attempt to acquire the exact same I_MUTEX_PARENT lock
already held by the task, resulting in the following recursive locking
deadlock:&lt;/p&gt;
&lt;p&gt;============================================
 WARNING: possible recursive locking detected
 6.12.0-55.27.1.el10_0.x86_64+debug #1 Not tainted
 --------------------------------------------
 mv/5099 is trying to acquire lock:
 ffff888132845358 (&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1){+.+.}-{3:3},
 at: __kern_path_locked+0x10a/0x2f0&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
 ffff888132846b58 (&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1){+.+.}-{3:3},
 at: lock_two_directories+0x13f/0x2b0&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
  Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
        ----
   lock(&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1);
   lock(&amp;amp;inode-&amp;gt;i_sb-&amp;gt;s_type-&amp;gt;i_mutex_dir_key/1);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68096</guid>
    </item>
  </channel>
</rss>
