CVE-2025-21829: RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]"
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Fix the warning "rxecleanup+0x12c/0x170 [rdmarxe]"
The Call Trace is as below: " <TASK> ? showregs.cold+0x1a/0x1f ? rxecleanup+0x12c/0x170 [rdmarxe] ? warn+0x84/0xd0 ? rxecleanup+0x12c/0x170 [rdmarxe] ? reportbug+0x105/0x180 ? handlebug+0x46/0x80 ? excinvalidop+0x19/0x70 ? asmexcinvalidop+0x1b/0x20 ? rxecleanup+0x12c/0x170 [rdmarxe] ? rxecleanup+0x124/0x170 [rdmarxe] rxedestroyqp.cold+0x24/0x29 [rdmarxe] ibdestroyqpuser+0x118/0x190 [ibcore] rdmadestroyqp.cold+0x43/0x5e [rdmacm] rtrscqqpdestroy.cold+0x1d/0x2b [rtrscore] rtrssrvclosework.cold+0x1b/0x31 [rtrsserver] processonework+0x21d/0x3f0 workerthread+0x4a/0x3c0 ? processonework+0x3f0/0x3f0 kthread+0xf0/0x120 ? kthreadcompleteandexit+0x20/0x20 retfromfork+0x22/0x30 </TASK> " When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly.
Compared with other rdma drivers, a bigger timeout is used.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Fix the warning "rxecleanup+0x12c/0x170 [rdmarxe]"
The Call Trace is as below: " TASK ? showregs.cold+0x1a/0x1f ? rxecleanup+0x12c/0x170 [rdmarxe] ? warn+0x84/0xd0 ? rxecleanup+0x12c/0x170 [rdmarxe] ? reportbug+0x105/0x180 ? handlebug+0x46/0x80 ? excinvalidop+0x19/0x70 ? asmexcinvalidop+0x1b/0x20 ? rxecleanup+0x12c/0x170 [rdmarxe] ? rxecleanup+0x124/0x170 [rdmarxe] rxedestroyqp.cold+0x24/0x29 [rdmarxe] ibdestroyqpuser+0x118/0x190 [ibcore] rdmadestroyqp.cold+0x43/0x5e [rdmacm] rtrscqqpdestroy.cold+0x1d/0x2b [rtrscore] rtrssrvclosework.cold+0x1b/0x31 [rtrsserver] processonework+0x21d/0x3f0 workerthread+0x4a/0x3c0 ? processonework+0x3f0/0x3f0 kthread+0xf0/0x120 ? kthreadcompleteandexit+0x20/0x20 retfromfork+0x22/0x30 /TASK " When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly.
Compared with other rdma drivers, a bigger timeout is used.
— IBM
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-21829?
CVE-2025-21829 has not been assigned a specific severity score, but it addresses a notable warning in the RDMA subsystem of the Linux kernel.
How do I fix CVE-2025-21829?
To fix CVE-2025-21829, you should update to the latest stable version of the Linux kernel that includes the patch for this vulnerability.
Who is affected by CVE-2025-21829?
CVE-2025-21829 affects systems running vulnerable versions of the Linux kernel utilizing the RDMA/rxe module.
What does CVE-2025-21829 involve?
CVE-2025-21829 involves a fix for a warning generated in the RDMA/rxe component of the Linux kernel during the cleanup process.
Is CVE-2025-21829 exploitable?
The details on the exploitability of CVE-2025-21829 are not specified, but it primarily addresses a warning rather than an active exploit path.