CVE-2023-53731: netlink: fix potential deadlock in netlink_set_err()
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 ***
Security readout for executives and security teams
Plain-English summary
CVE-2023-53731 is a Linux kernel netlink locking flaw that could cause a deadlock. In business terms, the main concern is local system instability or service disruption on affected Linux kernels, not confirmed data theft or remote compromise.
Executive priority
Handle through normal kernel patch management, with elevated priority for shared, multi-tenant, or availability-sensitive Linux systems. There is no source-backed evidence of active exploitation in the provided bundle.
Technical view
The issue is a possible IRQ lock inversion in netlink_set_err(), also addressed in __netlink_diag_dump(). The kernel fix adds IRQ-safe locking similar to earlier netlink_lock_table() hardening. The evidence comes from syzbot deadlock reporting and Linux stable commits.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or downstream kernels containing the vulnerable netlink code. The source bundle lists Linux as affected and provides multiple stable commit references; distribution-specific backport status is not included.
Exploitation context
The bundle does not show active exploitation, public weaponization, or CISA KEV listing. The trigger evidence is syzbot reporting of a possible deadlock, so treat this as a reliability and denial-of-service risk until vendor guidance says more.
Researcher notes
Focus review on net/netlink/af_netlink.c locking behavior around netlink_set_err() and __netlink_diag_dump(). The record names syzbot evidence and stable fixes, but does not provide CVSS, CWE, exploitability details, or distribution mapping.
Mitigation direction
Update affected Linux kernels using vendor or distribution security channels.
Prioritize systems with untrusted local users, containers, or high availability requirements.
Check distribution advisories for backported fixes matching the referenced stable commits.
Plan reboot or live-patching procedures according to normal kernel update policy.
Validation and detection
Inventory kernel versions across servers, appliances, and container hosts.
Compare installed kernels against distribution advisories for CVE-2023-53731.
Confirm whether vendor kernels include the referenced netlink IRQ-safety fixes.
Monitor for kernel deadlock warnings or unexplained network subsystem hangs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53731 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
10Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 22, 2025, 13:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.