Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocal access to RDMA-enabled host
-
ExploitFlood concurrent iwpm netlink requests
-
ExecutionWin refcount-before-init race (UAF)
-
ImpactCorrupt kernel memory to escalate privileges
Vulnerability Assessment
| Exploitation Conditions | Requires the RDMA/iWARP port mapper (iwpm) subsystem to be active - i.e., InfiniBand/RDMA hardware or software RDMA (rxe/siw) loaded and the iWARP port-mapper netlink interface in use - which is NOT the default on general-purpose desktop/server installs. The attacker needs local code execution with low privileges (PR:L) and must drive concurrent nlmsg_request operations to win the narrow race window between list_add_tail() exposing the object on the global list and the subsequent kref initialization (AC:H). Limiting factors: local-only (AV:L, no remote reach), no user interaction, dependence on a non-default RDMA stack, and the need to reliably win a timing race on an SMP system, all of which substantially constrain real-world exploitability. |
| Impact | This is a real but comparatively low-priority defensive issue despite its 7.0 (High) CVSS score. The CVSS vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H is internally consistent for a kernel race condition: AV:L means no remote reach, AC:H reflects the narrow timing window between list_add_tail() and kref initialization that an attacker must win, and PR:L means local low-privileged code must already be running. The full C:H/I:H/A:H impact is justified because a refcount 'addition on 0' bug leads to use-after-free and kernel memory corruption, which can escalate to full compromise. The exploitation signals argue AGAINST urgency, however: EPSS is only 0.22% (11th percentile), this is NOT on the CISA KEV list, and there is no public exploit identified at time of analysis. The 'Information Disclosure' tag conflicts with the I:H/A:H integrity and availability impacts in the CVSS vector - this is a memory-corruption/use-after-free class flaw, not a pure disclosure bug, so treat the tag as under-scoped. Net: a legitimate memory-safety fix worth patching in the normal cycle, but it requires pre-existing local access, a winnable race, and an active RDMA/iWARP stack, so it is not a drop-everything emergency. |
| Exploit ScenarioDerived | A local, low-privileged attacker on a Linux host with the RDMA/iWARP port mapper active issues many concurrent iwpm netlink requests to repeatedly hit the window where a nlmsg_request is added to the global list before its refcount is initialized. By winning this race on another CPU, the attacker triggers a 'kref_get on 0' use-after-free, corrupting kernel memory to pursue privilege escalation. No public exploit code is identified, and the high attack complexity (AC:H) and local-only vector make reliable exploitation difficult. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Refcount initialization ordering in the Linux kernel's RDMA iWARP port-mapper (iwpm) subsystem allows a local, low-privileged attacker to trigger a kref "addition on 0" race that can lead to premature object release and kernel memory corruption, rated 7.0 High (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Only systems that actually load and use the RDMA stack with iWARP port-mapper netlink traffic are exposed - the iwpm subsystem is not active on default desktop or server installs without InfiniBand/RDMA hardware or the software RDMA drivers (rxe, siw). Exploitation requires local code execution plus winning a narrow timing window on an SMP system, and no public exploit code or confirmed active exploitation has been identified at time of analysis; EPSS is 0.22% (11th percentile).
RemediationAI
Vendor-released patch: upgrade to a kernel version containing the fix - Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8, or 7.3-rc4 and later - or apply the corresponding stable commit referenced in the advisory links above (e.g., https://git.kernel.org/stable/c/88e429a4e9bac3d2138011c5ca06254331f2587f) and consume your distribution's updated kernel package once it carries the backport. Because AV:L and PR:L apply, the most effective compensating control on hosts that do not use RDMA is to shrink attack surface by preventing the iWARP port-mapper and RDMA stack from loading at all: blacklist or do not load the rdma_rxe, siw (Soft-iWARP), rdma_cm, iw_cm, and ib_core modules (modprobe.d blacklist plus removing them from initramfs), or disable RDMA entirely in the kernel config - the trade-off is that all RDMA/RoCE/iWARP functionality is lost on that host. Where RDMA must remain enabled on iWARP-capable hardware, restricting the iwpm netlink interface to trusted local processes (e.g., mandatory access control policy confining the iwarp-port-mapper userspace daemon so low-privileged accounts cannot drive concurrent nlmsg_request operations, or excluding untrusted local users entirely) reduces the window for a race, though it does not remove the underlying kernel bug and does not protect against a privileged local attacker; note that the race itself cannot be reliably eliminated from userspace, so kernel patching remains the definitive fix. Given no CISA KEV listing, no public exploit code, and an EPSS score of just 0.22%, remediation can be scheduled with normal patch cadence rather than as an emergency, prioritizing RDMA/iWARP-equipped hosts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw lives in drivers/infiniband/core/iwpm_util.c (RDMA/core), which implements the iWARP Port Mapper - the kernel-side service that maps iWARP/IP addresses and ports on behalf of iWARP-capable RDMA devices, communicating with userspace through a dedicated netlink family (IWPM_CMD / iwpm netlink socket). Each outstanding netlink request is represented by an nlmsg_request structure whose lifetime is managed by a kref reference counter and which is linked into a global request list under iwpm_nlmsg_req_lock. The vulnerable code called list_add_tail() to publish the object on that global list before invoking the kref initializer, so a concurrent CPU executing kref_get() on the freshly listed object could observe a zero reference count - the classic refcount "addition on 0" condition (with CONFIG_REFCOUNT_FULL / refcount_t this produces a warning and saturation; semantically it means the object can be freed while still referenced, i.e., a use-after-free primitive). The upstream fix moves kref initialization ahead of list_add_tail() and initializes all remaining structure fields before publication, restoring the invariant that an object is fully constructed before it becomes reachable by other CPUs. No CWE is supplied in the source data, but the defect class is improper reference-count management in a shared/global data structure leading to a lifetime (use-after-free) bug. The CPE records confirm the affected product as the upstream Linux kernel (cpe:2.3:a:linux:linux), with iWPM code present since Linux 3.16 (EUVD lists 3.16 as the earliest affected version).
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only kernel code path (AV:L) reachable by low-privileged users (PR:L); the refcount race needs a narrow winnable window (AC:H); use-after-free yields full memory-corruption impact (C/I/A:H).
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
4DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
RDMA/core: fix refcount bug in iwpm_get_nlmsg_request()
iwpm_get_nlmsg_request() initializes refcount _after_ list_add_tail() making it accessible to global list where another CPU can kref_get() on nlmsg_request causing a refcount "addition on 0" bug. Fix this by initializing kref _before_ list_add_tail() so refcount for nlmsg_request can be incremented/decremented normally. In addition, also initialize every field before list_add_tail().
Executive ViewAI
A high-severity vulnerability in the Linux kernel's RDMA iWARP port-mapper (iwpm) subsystem allows a local, low-privileged user to trigger kernel memory corruption, potentially leading to privilege escalation or system instability. Only systems that actively use RDMA/iWARP networking-such as high-performance computing clusters or specialized storage networks-are affected; standard desktop and server installations without these components are not exposed. No public exploit identified at time of analysis, and a patch is available per vendor advisory.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-93180
GHSA-vh89-8c9p-vvg2
NVD
CVE.org
EPSS
Exploit-DB