Answer in brief
CVE-2025-21829 records a Unknown severity vulnerability in RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]". The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <720653309dd31c8a927ef5d87964578ad544980f || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <45e567800492088bc52c9abac35524b4d332a8f8 || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <7a2de8126ed3801f2396720e10a03cd546a3cea1 || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <a7d15eaecf0d6e13226db629ae2401c8c02683e5 || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1 | 720653309dd31c8a927ef5d87964578ad544980f, 45e567800492088bc52c9abac35524b4d332a8f8, 7a2de8126ed3801f2396720e10a03cd546a3cea1, a7d15eaecf0d6e13226db629ae2401c8c02683e5, edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Mar 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-21829 records a Unknown severity vulnerability in RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]". The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <720653309dd31c8a927ef5d87964578ad544980f || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <45e567800492088bc52c9abac35524b4d332a8f8 || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <7a2de8126ed3801f2396720e10a03cd546a3cea1 || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <a7d15eaecf0d6e13226db629ae2401c8c02683e5 || >=215d0a755e1bcd92cbe6a71a21194ce7c82ec106 <edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1 | 720653309dd31c8a927ef5d87964578ad544980f, 45e567800492088bc52c9abac35524b4d332a8f8, 7a2de8126ed3801f2396720e10a03cd546a3cea1, a7d15eaecf0d6e13226db629ae2401c8c02683e5, edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Mar 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.