CVE-2023-53731: netlink: fix potential deadlock in netlink_set_err()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Fixed version: Linux Linux 1556ba034b95cfd4f75ea93c1a2679ae0444bba1, 4.10, 4.14.322.
Low priority for now. Upgrade to Linux Linux 1556ba034b95cfd4f75ea93c1a2679ae0444bba1, 4.10, 4.14.322 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 ***
- Published
- Oct 22, 2025
- Updated
- Oct 28, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5f155c4046200f067b1dc3140ea99ef56e4e0b74, a8e9111a8625dd11e70edd61f7a1ccd26c041442, 76cc8e04f38c2bbfcba07f62864a011f142bd40c, 5.13affected
- 82b2ea5f904b3826934df4a00f3b8806272185f6 and later · before c09e8e3f7fd432984bf5422302b093d2371dfc48affected · git
- 59fba11d649854134c75ad88c8adafa9304ac419 and later · before 4b9adb8d4a62ff7608d4a7d4eb42036a88f30980affected · git
- 21df0c2e7d195de4a3c650de9361b3037fa6c59a and later · before 8f6652ed2ad98fe6d13b903483d9257762ab2ec6affected · git
- 1d6d43d4805da9b3fa0f5841e8b1083c89868f35 and later · before cde7b90e0539a3b11da377e463dfd2288a162dbfaffected · git
- 1d482e666b8e74c7555dbdfbfb77205eeed3ff2d and later · before a641240b7e071c5538dc0e7894ece833fce459ddaffected · git
- 1d482e666b8e74c7555dbdfbfb77205eeed3ff2d and later · before 61ffe8b1ee084e5c82a4e4bbf9e7b68e0c06e464affected · git
- 1d482e666b8e74c7555dbdfbfb77205eeed3ff2d and later · before eb8e27c8fa9397b4a7b181c48fa58157dbe9902eaffected · git
- 1d482e666b8e74c7555dbdfbfb77205eeed3ff2d and later · before 1556ba034b95cfd4f75ea93c1a2679ae0444bba1affected · git
- 1d482e666b8e74c7555dbdfbfb77205eeed3ff2d and later · before 8d61f926d42045961e6b65191c09e3678d86a9cfaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.4-1 | 6.4.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-53729Oct 22, 2025 · soc: qcom: qmi_encdec: Restrict string length in decode31Monitor
- ← EarlierCVE-2023-53730Oct 22, 2025 · blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost0Monitor
- Later →CVE-2023-53732Oct 22, 2025 · fs/ntfs3: Fix NULL dereference in ni_write_inode0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1556ba034b95cfd4f75ea93c1a2679ae0444bba1 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.14.322 | Vendor (CNA) |
| Linux Linux | 4.19.291 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4b9adb8d4a62ff7608d4a7d4eb42036a88f30980 | Vendor (CNA) |
| Linux Linux | 5.10.188 | Vendor (CNA) |
| Linux Linux | 5.13 | Vendor (CNA) |
| Linux Linux | 5.4.251 | Vendor (CNA) |
| Linux Linux | 61ffe8b1ee084e5c82a4e4bbf9e7b68e0c06e464 | Vendor (CNA) |
| Linux Linux | 8d61f926d42045961e6b65191c09e3678d86a9cf | Vendor (CNA) |
| Linux Linux | 8f6652ed2ad98fe6d13b903483d9257762ab2ec6 | Vendor (CNA) |
| Linux Linux | a641240b7e071c5538dc0e7894ece833fce459dd | Vendor (CNA) |
| Linux Linux | c09e8e3f7fd432984bf5422302b093d2371dfc48 | Vendor (CNA) |
| Linux Linux | cde7b90e0539a3b11da377e463dfd2288a162dbf | Vendor (CNA) |
| Linux Linux | eb8e27c8fa9397b4a7b181c48fa58157dbe9902e | Vendor (CNA) |
| debian:linux | 6.1.52-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/4b9adb8d4a62ff7608d4a7d4eb42036a88f30980
- git.kernel.org/stable/c/61ffe8b1ee084e5c82a4e4bbf9e7b68e0c06e464
- git.kernel.org/stable/c/8d61f926d42045961e6b65191c09e3678d86a9cf
- git.kernel.org/stable/c/8f6652ed2ad98fe6d13b903483d9257762ab2ec6
- git.kernel.org/stable/c/a641240b7e071c5538dc0e7894ece833fce459dd
- git.kernel.org/stable/c/c09e8e3f7fd432984bf5422302b093d2371dfc48
- git.kernel.org/stable/c/cde7b90e0539a3b11da377e463dfd2288a162dbf
- git.kernel.org/stable/c/eb8e27c8fa9397b4a7b181c48fa58157dbe9902e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.