<?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>Tue, 29 Sep 2026 19:19:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53731 — netlink: fix potential deadlock in netlink_set_err()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53731</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;netlink: fix potential deadlock in netlink_set_err()&lt;/p&gt;
&lt;p&gt;syzbot reported a possible deadlock in netlink_set_err() [1]&lt;/p&gt;
&lt;p&gt;A similar issue was fixed in commit 1d482e666b8e (&amp;#34;netlink: disable IRQs
for netlink_lock_table()&amp;#34;) in netlink_lock_table()&lt;/p&gt;
&lt;p&gt;This patch adds IRQ safety to netlink_set_err() and __netlink_diag_dump()
which were not covered by cited commit.&lt;/p&gt;
&lt;p&gt;[1]&lt;/p&gt;
&lt;p&gt;WARNING: possible irq lock inversion dependency detected
6.4.0-rc6-syzkaller-00240-g4e9f0ec38852 #0 Not tainted&lt;/p&gt;
&lt;p&gt;syz-executor.2/23011 just changed the state of lock:
ffffffff8e1a7a58 (nl_table_lock){.+.?}-{2:2}, at: netlink_set_err+0x2e/0x3a0 net/netlink/af_netlink.c:1612
but this lock was taken by another, SOFTIRQ-safe lock in the past:
 (&amp;amp;local-&amp;gt;queue_stop_reason_lock){..-.}-{2:2}&lt;/p&gt;
&lt;p&gt;and interrupts could create inverse lock ordering between them.&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible interrupt unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(nl_table_lock);
                               local_irq_disable();
                               lock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);
                               lock(nl_table_lock);
  &amp;lt;Interrupt&amp;gt;
    lock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&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;netlink: fix potential deadlock in netlink_set_err()&lt;/p&gt;
&lt;p&gt;syzbot reported a possible deadlock in netlink_set_err() [1]&lt;/p&gt;
&lt;p&gt;A similar issue was fixed in commit 1d482e666b8e (&amp;#34;netlink: disable IRQs
for netlink_lock_table()&amp;#34;) in netlink_lock_table()&lt;/p&gt;
&lt;p&gt;This patch adds IRQ safety to netlink_set_err() and __netlink_diag_dump()
which were not covered by cited commit.&lt;/p&gt;
&lt;p&gt;[1]&lt;/p&gt;
&lt;p&gt;WARNING: possible irq lock inversion dependency detected
6.4.0-rc6-syzkaller-00240-g4e9f0ec38852 #0 Not tainted&lt;/p&gt;
&lt;p&gt;syz-executor.2/23011 just changed the state of lock:
ffffffff8e1a7a58 (nl_table_lock){.+.?}-{2:2}, at: netlink_set_err+0x2e/0x3a0 net/netlink/af_netlink.c:1612
but this lock was taken by another, SOFTIRQ-safe lock in the past:
 (&amp;amp;local-&amp;gt;queue_stop_reason_lock){..-.}-{2:2}&lt;/p&gt;
&lt;p&gt;and interrupts could create inverse lock ordering between them.&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible interrupt unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(nl_table_lock);
                               local_irq_disable();
                               lock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);
                               lock(nl_table_lock);
  &amp;lt;Interrupt&amp;gt;
    lock(&amp;amp;local-&amp;gt;queue_stop_reason_lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53731</guid>
    </item>
  </channel>
</rss>
