KernelScan.io

HIGH Introduced in 3.16

rdma NlmsgRequest Race

CVE-2026-98252

CVSS 7.0 / 10.0 NVD

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

KernelScan AI6.9MEDIUM

01

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().

02

Engine v0.7.0

Risk summary

A local user who can initiate iWARP RDMA connections can trigger a race in the iWARP Port Mapper that corrupts a reference count, potentially leading to use-after-free memory corruption. Exploitation requires the RDMA subsystem to be active and an iWARP-capable device (hardware or software) to be available. The resulting memory corruption could allow privilege escalation or a kernel panic.

Affecteddrivers/infiniband/core/iwpm_util.c (RDMA iWARP Port Mapper)

Vulnerability analysis

A newly allocated netlink message request object is placed on a globally visible linked list before its reference count and other fields are initialized. Another CPU traversing the list can attempt to increment the reference count before initialization has completed, hitting a zero refcount and corrupting the object's lifecycle tracking. This can cause the object to be freed prematurely while other threads still hold pointers to it, leading to use-after-free memory corruption. The fix initializes every field including the reference count before the object is added to the shared list, closing the race window entirely. The vulnerable code path is reachable from local users who can initiate iWARP RDMA connections, which requires the RDMA subsystem to be loaded and an iWARP-capable device (hardware NIC or software emulation) to be configured on the system.

03

BranchIntroducedFixed inPatch commit
5.103.165.10.27152c13c63bb36
5.153.165.15.2228a91609032d4
6.13.166.1.189ce8a379598bd
6.123.166.12.11288e429a4e9ba
6.183.166.18.54e15eb536be4f
6.63.166.6.1582fbac8a56004
7.23.167.2.8117871cdb892
mainline3.167.333fb59da49c4
cip/4.193.164.19.325-cip1373751060c05b2
cip/4.19-rt3.164.19.325-cip137-rt513751060c05b2
cip/5.103.165.10.271-cip7852c13c63bb36
cip/5.10-rt3.165.10.272-cip79-rt3552c13c63bb36
cip/6.13.166.1.189-cip61ce8a379598bd
cip/6.1-rt3.166.1.189-cip61-rt32ce8a379598bd
cip/6.123.166.12.112-cip3388e429a4e9ba

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.112-cip33
cip/6.1Fixed in 6.1.189-cip61
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.271-cip78
cip/5.10-rtFixed in 5.10.272-cip79-rt35
cip/4.19Fixed in 4.19.325-cip137
cip/4.19-rtFixed in 4.19.325-cip137-rt51
cip/4.4Affected — no CIP fix yet (latest 4.4.302-cip116)
cip/4.4-rtAffected — no CIP fix yet (latest 4.4.302-cip115-rt63)