CVE-2023-53731

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netlink: fix potential deadlock in netlink_set_err()<br /> <br /> syzbot reported a possible deadlock in netlink_set_err() [1]<br /> <br /> A similar issue was fixed in commit 1d482e666b8e ("netlink: disable IRQs<br /> for netlink_lock_table()") in netlink_lock_table()<br /> <br /> This patch adds IRQ safety to netlink_set_err() and __netlink_diag_dump()<br /> which were not covered by cited commit.<br /> <br /> [1]<br /> <br /> WARNING: possible irq lock inversion dependency detected<br /> 6.4.0-rc6-syzkaller-00240-g4e9f0ec38852 #0 Not tainted<br /> <br /> syz-executor.2/23011 just changed the state of lock:<br /> ffffffff8e1a7a58 (nl_table_lock){.+.?}-{2:2}, at: netlink_set_err+0x2e/0x3a0 net/netlink/af_netlink.c:1612<br /> but this lock was taken by another, SOFTIRQ-safe lock in the past:<br /> (&amp;local-&gt;queue_stop_reason_lock){..-.}-{2:2}<br /> <br /> and interrupts could create inverse lock ordering between them.<br /> <br /> other info that might help us debug this:<br /> Possible interrupt unsafe locking scenario:<br /> <br /> CPU0 CPU1<br /> ---- ----<br /> lock(nl_table_lock);<br /> local_irq_disable();<br /> lock(&amp;local-&gt;queue_stop_reason_lock);<br /> lock(nl_table_lock);<br /> <br /> lock(&amp;local-&gt;queue_stop_reason_lock);<br /> <br /> *** DEADLOCK ***