LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21886: RDMA/mlx5: Fix implicit ODP hang on parent deregistration

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix implicit ODP hang on parent deregistration Fix the destroy_unused_implicit_child_mr() to prevent hanging during parent deregistration as of below [1]. Upon entering destroy_unused_implicit_child_mr(), the reference count for the implicit MR parent is incremented using: refcount_inc_not_zero(). A corresponding decrement must be performed if free_implicit_child_mr_work() is not called. The code has been updated to properly manage the reference count that was incremented. [1] INFO: task python3:2157 blocked for more than 120 seconds. Not tainted 6.12.0-rc7+ #1633 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:python3 state:D stack:0 pid:2157 tgid:2157 ppid:1685 flags:0x00000000 Call Trace: <TASK> __schedule+0x420/0xd30 schedule+0x47/0x130 __mlx5_ib_dereg_mr+0x379/0x5d0 [mlx5_ib] ? __pfx_autoremove_wake_function+0x10/0x10 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+0xc1/0x2f0 ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0x116/0x170 [ib_uverbs] ? lock_release+0xc6/0x280 ib_uverbs_ioctl+0xe7/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] __x64_sys_ioctl+0x1b0/0xa70 ? kmem_cache_free+0x221/0x400 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f20f21f017b RSP: 002b:00007ffcfc4a77c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffcfc4a78d8 RCX: 00007f20f21f017b RDX: 00007ffcfc4a78c0 RSI: 00000000c0181b01 RDI: 0000000000000003 RBP: 00007ffcfc4a78a0 R08: 000056147d125190 R09: 00007f20f1f14c60 R10: 0000000000000001 R11: 0000000000000246 R12: 00007ffcfc4a7890 R13: 000000000000001c R14: 000056147d100fc0 R15: 00007f20e365c9d0 </TASK>

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make affected systems hang while cleaning up RDMA memory registrations. The business concern is availability: specialized servers using mlx5 RDMA hardware could stall workloads or require operational intervention. The source bundle does not show active exploitation, CVSS scoring, or broad internet exposure.

Executive priority

Schedule remediation for RDMA-enabled infrastructure during the next operational patch window, sooner for critical HPC, storage, AI, or low-latency environments. This is not evidenced as internet-wormable or actively exploited, but hangs in core compute infrastructure can be disruptive.

Technical view

The flaw is in RDMA/mlx5 implicit On-Demand Paging teardown. destroy_unused_implicit_child_mr() increments the implicit parent memory-region reference count but previously failed to decrement it when free_implicit_child_mr_work() was not called, causing hangs during parent deregistration through the ib_uverbs path.

Likely exposure

Most relevant exposure is Linux hosts using Mellanox mlx5 RDMA with implicit ODP-capable RDMA workloads. General Linux systems without RDMA/mlx5 use are less likely to be affected. The bundle lists Linux 6.12.13 and 6.13.2 as unaffected.

Exploitation context

The provided evidence shows a blocked task and kernel call trace, not a public exploit. KEV is false, and the bundle provides no CVSS, CWE, or active exploitation report. Treat this as a potential local or workload-triggered availability issue until vendor guidance says more.

Researcher notes

Key indicators are mlx5_ib deregistration, implicit ODP memory regions, parent MR deregistration, and reference-count imbalance. The source bundle does not define affected distribution packages, exploit prerequisites, or exact introduced kernel releases beyond listed commits and fixed stable references.

Mitigation direction

  • Update affected Linux kernels to a version containing the referenced stable fixes.
  • Prioritize mlx5 RDMA servers running user-space RDMA workloads.
  • Check distribution kernel advisories for backported fixes.
  • Consider reducing exposure of nonessential RDMA workloads until patched.

Validation and detection

  • Inventory Linux hosts with mlx5 RDMA drivers and RDMA workloads.
  • Check kernel versions against vendor fixed packages or stable commits.
  • Review logs for hung tasks involving mlx5_ib, ib_core, or ib_uverbs.
  • Confirm fixed versions such as 6.12.13 or 6.13.2 where applicable.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-21886 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7cc8f681f6d4ae4478ae0f60485fc768f2b450da, edfb65dbb9ffd3102f3ff4dd21316158e56f1976, d3d930411ce390e532470194296658a960887773unaffected
LinuxLinux6.12.13, 6.13.2unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.