---
id: CVE-2025-21829
title: |-
  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 [rdm…
summary: |-
  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 [rdm…
severity: critical
cvss: 9.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 6.0, < 6.1.129'
  - 'linux_kernel >= 6.2, < 6.6.76'
  - 'linux_kernel >= 6.7, < 6.12.13'
  - 'linux_kernel >= 6.13, < 6.13.2'
patched:
  - linux_kernel 6.13.2
published: '2025-03-06'
updated: '2026-07-30'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-21829'
references:
  - url: 'https://git.kernel.org/stable/c/45e567800492088bc52c9abac35524b4d332a8f8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/720653309dd31c8a927ef5d87964578ad544980f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7a2de8126ed3801f2396720e10a03cd546a3cea1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a7d15eaecf0d6e13226db629ae2401c8c02683e5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
epss: 0.00397
epssPercentile: 0.33765
ingestedAt: '2026-07-30T06:53:10.327Z'
---

## Overview

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.

## Affected

- `linux_kernel >= 6.0, < 6.1.129`
- `linux_kernel >= 6.2, < 6.6.76`
- `linux_kernel >= 6.7, < 6.12.13`
- `linux_kernel >= 6.13, < 6.13.2`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.13.2`