lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025030611-CVE-2025-21829-50f9@gregkh> Date: Thu, 6 Mar 2025 17:08:12 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2025-21829: RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]" Description =========== 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. The Linux kernel CVE team has assigned CVE-2025-21829 to this issue. Affected and fixed versions =========================== Issue introduced in 6.0 with commit 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 and fixed in 6.1.129 with commit 720653309dd31c8a927ef5d87964578ad544980f Issue introduced in 6.0 with commit 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 and fixed in 6.6.76 with commit 45e567800492088bc52c9abac35524b4d332a8f8 Issue introduced in 6.0 with commit 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 and fixed in 6.12.13 with commit 7a2de8126ed3801f2396720e10a03cd546a3cea1 Issue introduced in 6.0 with commit 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 and fixed in 6.13.2 with commit a7d15eaecf0d6e13226db629ae2401c8c02683e5 Issue introduced in 6.0 with commit 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 and fixed in 6.14-rc1 with commit edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-21829 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/infiniband/sw/rxe/rxe_pool.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/720653309dd31c8a927ef5d87964578ad544980f https://git.kernel.org/stable/c/45e567800492088bc52c9abac35524b4d332a8f8 https://git.kernel.org/stable/c/7a2de8126ed3801f2396720e10a03cd546a3cea1 https://git.kernel.org/stable/c/a7d15eaecf0d6e13226db629ae2401c8c02683e5 https://git.kernel.org/stable/c/edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1
Powered by blists - more mailing lists