cve.bz

CVE-2025-21892 linux linux kernel: Race Condition

4.7 mediumEPSS 0.2%Fix available

Medium (4.7) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix the recovery flow of the UMR QP This patch addresses an issue in the recovery flow of the UMR QP, ensuring tasks do not get stuck, as highlighted by the call trace [1]. During recovery, before transitioning the QP to the RESET state, the software must wait for all outstanding WRs to complete. Failing to do so can cause the firmware to skip sending some flushed CQEs with errors and simply discard them upon the RESET, as per the IB specification. This race condition can result in lost CQEs and tasks becoming stuck. To resolve this, the patch sends a final WR which serves only as a barrier before moving the QP state to RESET. Once a CQE is received for that final WR, it guarantees that no outstanding WRs remain, making it safe to transition the QP to RESET and subsequently back to RTS, restoring proper functionality. Note: For the barrier WR, we simply reuse the failed and ready WR. Since the QP is in an error state, it will only receive IB_WC_WR_FLUSH_ERR. However, as it serves only as a barrier we don't care about its status. [1] INFO: task rdma_resource_l:1922 blocked for more than 120 seconds. Tainted: G W 6.12.0-rc7+ #1626 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:rdma_resource_l state:D stack:0 pid:1922 tgid:1922 ppid:1369 flags:0x00004004 Call Trace: <TASK> __schedule+0x420/0xd30 schedule+0x47/0x130 schedule_timeout+0x280/0x300 ? mark_held_locks+0x48/0x80 ? lockdep_hardirqs_on_prepare+0xe5/0x1a0 wait_for_completion+0x75/0x130 mlx5r_umr_post_send_wait+0x3c2/0x5b0 [mlx5_ib] ? __pfx_mlx5r_umr_done+0x10/0x10 [mlx5_ib] mlx5r_umr_revoke_mr+0x93/0xc0 [mlx5_ib] __mlx5_ib_dereg_mr+0x299/0x520 [mlx5_ib] ? _raw_spin_unlock_irq+0x24/0x40 ? wait_for_completion+0xfe/0x130 ? rdma_restrack_put+0x63/0xe0 [ib_core] ib_dereg_mr_user+0x5f/0x120 [ib_core] ? lock_release+0xc6/0x280 destroy_hw_idr_uobject+0x1d/0x60 [ib_uverbs] uverbs_destroy_uobject+0x58/0x1d0 [ib_uverbs] uobj_destroy+0x3f/0x70 [ib_uverbs] ib_uverbs_cmd_verbs+0x3e4/0xbb0 [ib_uverbs] ? __pfx_uverbs_destroy_def_handler+0x10/0x10 [ib_uverbs] ? __lock_acquire+0x64e/0x2080 ? mark_held_locks+0x48/0x80 ? find_held_lock+0x2d/0xa0 ? lock_acquire+0xc1/0x2f0 ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] ? __fget_files+0xc3/0x1b0 ib_uverbs_ioctl+0xe7/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] __x64_sys_ioctl+0x1b0/0xa70 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f99c918b17b RSP: 002b:00007ffc766d0468 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffc766d0578 RCX: 00007f99c918b17b RDX: 00007ffc766d0560 RSI: 00000000c0181b01 RDI: 0000000000000003 RBP: 00007ffc766d0540 R08: 00007f99c8f99010 R09: 000000000000bd7e R10: 00007f99c94c1c70 R11: 0000000000000246 R12: 00007ffc766d0530 R13: 000000000000001c R14: 0000000040246a80 R15: 0000000000000000 </TASK>

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-21892 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-21892?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-21892?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-21892 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 5.19.10 before 5.20
Linux6.0 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.160
Linux6.126.12.18
Linux6.136.13.6
Linuxlater releases6.14

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2025-21892
Debian13, 14linux6.12.19-1DEBIAN-CVE-2025-21892
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-21892
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-21892
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-21892
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1039.41~22.04.1UBUNTU-CVE-2025-21892 USN-7766-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1036.42~22.04.1UBUNTU-CVE-2025-21892 USN-7802-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1040.42~22.04.1UBUNTU-CVE-2025-21892 USN-7766-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-85.85~22.04.1UBUNTU-CVE-2025-21892 USN-7764-2 USN-7801-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1037.37~22.04.1UBUNTU-CVE-2025-21892 USN-7779-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-84.84.1~22.04.1UBUNTU-CVE-2025-21892 USN-7764-1
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1039.42~22.04.1UBUNTU-CVE-2025-21892 USN-7765-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1037.38~22.04.1UBUNTU-CVE-2025-21892 USN-7801-3
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-21892
29 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6, Linux Enterprise Module for Legacy 15 SP6 and 1 morekernel-default6.4.0-150600.23.47.2SUSE-SU-2025:1180-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.3.1SUSE-SU-2025:01951-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_101-150600.1.5.1SUSE-SU-2025:1178-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_101-150600.13.5.1SUSE-SU-2025:1180-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_11-150700.15.3.1SUSE-SU-2025:01951-1
SUSELinux Enterprise Module for Basesystem 15 SP6kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150600.23.47.2SUSE-SU-2025:1180-1
SUSELinux Enterprise Module for Basesystem 15 SP6kernel-default-base6.4.0-150600.23.47.2.150600.12.20.2SUSE-SU-2025:1180-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.3.1SUSE-SU-2025:01951-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.3.1.150700.17.2.1SUSE-SU-2025:01951-1
SUSELinux Enterprise Module for Confidential Computing Technical Preview 15 SP6kernel-coco, kernel-syms-coco, kernel-coco_debug and 1 more6.4.0-15061.21.coco15sp6.1SUSE-SU-2025:01919-1
SUSELinux Enterprise Module for Development Tools 15 SP6kernel-docs, kernel-syms, kernel-obs-build6.4.0-150600.23.47.1SUSE-SU-2025:1180-1
SUSELinux Enterprise Module for Development Tools 15 SP6kernel-source6.4.0-150600.23.47.2SUSE-SU-2025:1180-1
15 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.6dtb-aarch64, kernel-docs, kernel-syms and 2 more6.4.0-150600.23.47.1SUSE-SU-2025:1180-1
openSUSELeap 15.6kernel-64kb, kernel-debug, kernel-source and 3 more6.4.0-150600.23.47.2SUSE-SU-2025:1180-1
openSUSELeap 15.6kernel-azure, kernel-source-azure6.4.0-150600.8.34.2SUSE-SU-2025:1177-1
openSUSELeap 15.6kernel-default-base6.4.0-150600.23.47.2.150600.12.20.2SUSE-SU-2025:1180-1
openSUSELeap 15.6kernel-rt, kernel-syms-rt, kernel-rt_debug and 1 more6.4.0-150600.10.34.1SUSE-SU-2025:1178-1
openSUSELeap 15.6kernel-syms-azure6.4.0-150600.8.34.1SUSE-SU-2025:1177-1
Azure Linux3kernelno fix listedAZL-62678
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2025-21892
Alpaquita25linux-lts6.12.41-r0BELL-CVE-2025-21892
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-21892

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The bug could happen if Mellanox Connect-IB Infiniband being used (would not be actual if hardware Mellanox Connect-IB PCI Express host channel adapter not available). The result of potential fail is that specific tasks can stuck. The security impact is limited, because it doesn't lead to crash or kernel panic.

Red Hat's mitigation

To mitigate this issue, prevent module mlx5_ib from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelOut of support scope
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelOut of support scope
Red Hat Enterprise Linux 8kernel-rtOut of support scope
Red Hat Enterprise Linux 9kernelOut of support scope
Red Hat Enterprise Linux 9kernel-rtOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-21892.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON