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 "__rxe_cleanup+0x12c/0x170 [rdma_rxe]"
The Call Trace is as below:
"
<TASK>
? show_regs.cold+0x1a/0x1f
? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
? __warn+0x84/0xd0
? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
? report_bug+0x105/0x180
? handle_bug+0x46/0x80
? exc_invalid_op+0x19/0x70
? asm_exc_invalid_op+0x1b/0x20
? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
? __rxe_cleanup+0x124/0x170 [rdma_rxe]
rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe]
ib_destroy_qp_user+0x118/0x190 [ib_core]
rdma_destroy_qp.cold+0x43/0x5e [rdma_cm]
rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core]
rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server]
process_one_work+0x21d/0x3f0
worker_thread+0x4a/0x3c0
? process_one_work+0x3f0/0x3f0
kthread+0xf0/0x120
? kthread_complete_and_exit+0x20/0x20
ret_from_fork+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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the software RDMA driver rxe. Under heavy RDMA resource allocation, cleanup can time out before resources are released, triggering kernel warnings during queue pair teardown. The public record does not provide CVSS severity or evidence of active exploitation.
Executive priority
Handle through normal Linux kernel patch governance, with higher priority for RDMA-enabled storage or compute infrastructure. There is no public evidence here of active exploitation, but affected systems may face reliability issues under resource pressure.
Technical view
CVE-2025-21829 is a Linux kernel RDMA/rxe cleanup timing flaw. The cited call trace shows __rxe_cleanup warnings during RDMA queue pair destruction, with RTRS-related teardown in the stack. The fix aligns rxe cleanup timeout behavior with other RDMA drivers by using a larger timeout.
Likely exposure
Exposure is most likely on Linux systems using RDMA/rxe, especially workloads creating many RDMA resources. Systems without RDMA/rxe enabled or without affected kernel builds are less likely exposed. The source lists Linux kernel versions and stable commits but does not map every distribution package.
Exploitation context
The source describes a reliability failure during resource cleanup, not privilege escalation or remote code execution. KEV is false, and no cited source states active exploitation. Treat this as operational stability risk until vendor advisories provide more detail.
Researcher notes
Evidence is limited to the CVE description, Linux stable fix references, and Debian LTS notice. The record lacks CVSS, CWE, exploitability analysis, and distribution-level version mapping. Do not infer impact beyond RDMA/rxe cleanup reliability without additional vendor data.
Mitigation direction
Apply vendor kernel updates containing the referenced stable RDMA/rxe fix.
Prioritize systems using RDMA/rxe or RTRS-related storage workloads.
If patching is delayed, review whether RDMA/rxe is required on affected hosts.
Monitor vendor advisories for distribution-specific fixed package versions.
Avoid direct deployment shortcuts; follow normal kernel change controls.
Validation and detection
Inventory kernels and compare against vendor advisories for CVE-2025-21829.
Check whether rdma_rxe is loaded or configured on Linux hosts.
Review logs for __rxe_cleanup warnings during RDMA teardown.
Confirm updated kernels include one of the referenced stable fixes.
Regression-test RDMA workloads that create many resources.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21829 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 6, 2025, 16:08 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.