HIGH Introduced in 3.16
rdma NlmsgRequest Race
CVE-2026-98252
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI6.9MEDIUM
01Description
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().
02KernelScan AI Analysis
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.
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.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 5.10 | 3.16 | 5.10.271 | 52c13c63bb36 |
| 5.15 | 3.16 | 5.15.222 | 8a91609032d4 |
| 6.1 | 3.16 | 6.1.189 | ce8a379598bd |
| 6.12 | 3.16 | 6.12.112 | 88e429a4e9ba |
| 6.18 | 3.16 | 6.18.54 | e15eb536be4f |
| 6.6 | 3.16 | 6.6.158 | 2fbac8a56004 |
| 7.2 | 3.16 | 7.2.8 | 117871cdb892 |
| mainline | 3.16 | 7.3 | 33fb59da49c4 |
| cip/4.19 | 3.16 | 4.19.325-cip137 | 3751060c05b2 |
| cip/5.10 | 3.16 | 5.10.271-cip78 | 52c13c63bb36 |
| cip/5.10-rt | 3.16 | 5.10.272-cip79-rt35 | 52c13c63bb36 |
| cip/6.1 | 3.16 | 6.1.189-cip61 | ce8a379598bd |
| cip/6.1-rt | 3.16 | 6.1.189-cip61-rt32 | ce8a379598bd |
| cip/6.12 | 3.16 | 6.12.112-cip33 | 88e429a4e9ba |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.112-cip33 |
| cip/6.1 | Fixed in 6.1.189-cip61 |
| cip/6.1-rt | Fixed in 6.1.189-cip61-rt32 |
| cip/5.10 | Fixed in 5.10.271-cip78 |
| cip/5.10-rt | Fixed in 5.10.272-cip79-rt35 |
| cip/4.19 | Fixed in 4.19.325-cip137 |
| cip/4.19-rt | Affected — no CIP fix yet (latest 4.19.325-cip136-rt50) |
| cip/4.4 | Affected — no CIP fix yet (latest 4.4.302-cip115) |
| cip/4.4-rt | Affected — no CIP fix yet (latest 4.4.302-cip115-rt63) |