CVE-2023-53731

netlink: fix potential deadlock in netlink_set_err()

N/A
Published: October 22, 2025 at 01:23 PM UTC
Updated: October 28, 2026 at 07:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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} and interrupts could create inverse lock ordering between them. other info that might help us debug this: Possible interrupt unsafe locking scenario: CPU0 CPU1 ---- ---- lock(nl_table_lock); local_irq_disable(); lock(&local->queue_stop_reason_lock); lock(nl_table_lock); <Interrupt> lock(&local->queue_stop_reason_lock); *** DEADLOCK ***

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14.237 ≤ v < 4.14.3224.19.195 ≤ v < 4.19.2914.4.273 ≤ v < 4.54.9.273 ≤ v < 4.105.10.44 ≤ v < 5.10.1885.12.11 ≤ v < 5.135.4.126 ≤ v < 5.4.2511d482e666b8e74c7555dbdfbfb77205eeed3ff2d1d6d43d4805da9b3fa0f5841e8b1083c89868f3521df0c2e7d195de4a3c650de9361b3037fa6c59a4.14.2374.19.1954.4.2734.9.2735.10.445.12.115.135.4.12659fba11d649854134c75ad88c8adafa9304ac4195f155c4046200f067b1dc3140ea99ef56e4e0b7476cc8e04f38c2bbfcba07f62864a011f142bd40c82b2ea5f904b3826934df4a00f3b8806272185f6a8e9111a8625dd11e70edd61f7a1ccd26c041442
Vendor states this is fixed in 1556ba034b95cfd4f75ea93c1a2679ae0444bba1 (fixed)
Vendor states this is fixed in 4b9adb8d4a62ff7608d4a7d4eb42036a88f30980 (fixed)
Vendor states this is fixed in 61ffe8b1ee084e5c82a4e4bbf9e7b68e0c06e464 (fixed)
Vendor states this is fixed in 8d61f926d42045961e6b65191c09e3678d86a9cf (fixed)
Vendor states this is fixed in 8f6652ed2ad98fe6d13b903483d9257762ab2ec6 (fixed)
Vendor states this is fixed in a641240b7e071c5538dc0e7894ece833fce459dd (fixed)
Vendor states this is fixed in c09e8e3f7fd432984bf5422302b093d2371dfc48 (fixed)
Vendor states this is fixed in cde7b90e0539a3b11da377e463dfd2288a162dbf (fixed)
Vendor states this is fixed in eb8e27c8fa9397b4a7b181c48fa58157dbe9902e (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.14.322 (unaffected)
Vendor states this is fixed in 4.19.291 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.188 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.121 (unaffected)
Vendor states this is fixed in 5.4.251 (unaffected)
Vendor states this is fixed in 6.1.39 (unaffected)
Vendor states this is fixed in 6.3.13 (unaffected)
Vendor states this is fixed in 6.4.4 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card