Vulnerability · Published Feb 27, 2025 · Assigned by Linux

CVE-2025-21732RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error

Medium 4.7

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)4.7Medium
Exploit odds (30 days)0.1%top 96.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error This patch addresses a race condition for an ODP MR that can result in a CQE with an error on the UMR QP. During the __mlx5_ib_dereg_mr() flow, the following sequence of calls occurs: mlx5_revoke_mr() mlx5r_umr_revoke_mr() mlx5r_umr_post_send_wait() At this point, the lkey is freed from the hardware's perspective. However, concurrently, mlx5_ib_invalidate_range() might be triggered by another task attempting to invalidate a range for the same freed lkey. This task will: - Acquire the umem_odp->umem_mutex lock. - Call mlx5r_umr_update_xlt() on the UMR QP. - Since the lkey has already been freed, this can lead to a CQE error, causing the UMR QP to enter an error state [1]. To resolve this race condition, the umem_odp->umem_mutex lock is now also acquired as part of the mlx5_revoke_mr() scope. Upon successful revoke, we set umem_odp->private which points to that MR to NULL, preventing any further invalidation attempts on its lkey. [1] From dmesg: infiniband rocep8s0f0: dump_cqe:277:(pid 0): WC error: 6, Message: memory bind operation error cqe_dump: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000030: 00 00 00 00 08 00 78 06 25 00 11 b9 00 0e dd d2 WARNING: CPU: 15 PID: 1506 at drivers/infiniband/hw/mlx5/umr.c:394 mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] Modules linked in: ip6table_mangle ip6table_natip6table_filter ip6_tables iptable_mangle xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_umad ib_ipoib ib_cm mlx5_ib ib_uverbs ib_core fuse mlx5_core CPU: 15 UID: 0 PID: 1506 Comm: ibv_rc_pingpong Not tainted 6.12.0-rc7+ #1626 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] [..] Call Trace: <TASK> mlx5r_umr_update_xlt+0x23c/0x3e0 [mlx5_ib] mlx5_ib_invalidate_range+0x2e1/0x330 [mlx5_ib] __mmu_notifier_invalidate_range_start+0x1e1/0x240 zap_page_range_single+0xf1/0x1a0 madvise_vma_behavior+0x677/0x6e0 do_madvise+0x1a2/0x4b0 __x64_sys_madvise+0x25/0x30 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2025-21732
Debian:13linux6.12.15-1DEBIAN-CVE-2025-21732
Debian:14linux6.12.15-1DEBIAN-CVE-2025-21732
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux6.8.0-64.67UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-aws6.8.0-1032.34UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1032.34~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-azure6.8.0-1034.39UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1015.15~24.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1034.39~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-azure-nvidia6.8.0-1022.23UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-gcp6.8.0-1033.35UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1015.15~24.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1033.35~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-gke6.8.0-1028.32UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1015.17UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-26.26~24.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-64.67~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-ibm6.8.0-1029.29UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1029.29~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-64.67.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1014.15~24.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-64.67.1~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1031.34UBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1010.10UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1031.34~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1031.34.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1008.8UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1022.22UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-oem-6.86.8.0-1031.31UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-oracle6.8.0-1029.30UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1029.30~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-raspi6.8.0-1031.35UBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-64.67~22.04.1UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-21732
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1017.18UBUNTU-CVE-2025-21732
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2025-21732

Affected products (as reported)

VendorProductVersions
Linux Linux e6fb246ccafbdfc86e0750af021628132fdbceac – before 63126215de7beebb662fcef7c7558c795000c904e6fb246ccafbdfc86e0750af021628132fdbceac – before b13d32786acabf70a7b04ed24b7468fc3c82977ce6fb246ccafbdfc86e0750af021628132fdbceac – before 5297f5ddffef47b94172ab0d3d62270002a3dcc1e6fb246ccafbdfc86e0750af021628132fdbceac – before abb604a1a9c87255c7a6f3b784410a9707baf467
Linux Linux 5.13

References