netlink: fix potential deadlock in netlink_set_err()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1d482e666b8e74c7555dbdfbfb77205eeed3ff2d · < 61ffe8b1ee084e5c82a4e4bbf9e7b68e0c06e464| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netlink: fix potential deadlock in netlink_set_err()
syzbot reported a possible deadlock in netlink_set_err() [1]
A similar issue was fixed in commit 1d482e666b8e ("netlink: disable IRQs for netlink_lock_table()") in netlink_lock_table()
This patch adds IRQ safety to netlink_set_err() and __netlink_diag_dump() which were not covered by cited commit.
[1]
WARNING: possible irq lock inversion dependency detected 6.4.0-rc6-syzkaller-00240-g4e9f0ec38852 #0 Not tainted
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: (&local->queue_stop_reason_lock){..-.}-{2:2}
From the CVE record · Linux
The Linux kernel has a potential deadlock in netlink_set_err() and __netlink_diag_dump() because their locking is not IRQ-safe. An interrupt occurring during an inverse lock ordering could trigger the deadlock; the input does not establish whether an attacker can trigger it or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their versions; the affected versions are not specified.