LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22010: RDMA/hns: Fix soft lockup during bt pages loop

In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix soft lockup during bt pages loop Driver runs a for-loop when allocating bt pages and mapping them with buffer pages. When a large buffer (e.g. MR over 100GB) is being allocated, it may require a considerable loop count. This will lead to soft lockup: watchdog: BUG: soft lockup - CPU#27 stuck for 22s! ... Call trace: hem_list_alloc_mid_bt+0x124/0x394 [hns_roce_hw_v2] hns_roce_hem_list_request+0xf8/0x160 [hns_roce_hw_v2] hns_roce_mtr_create+0x2e4/0x360 [hns_roce_hw_v2] alloc_mr_pbl+0xd4/0x17c [hns_roce_hw_v2] hns_roce_reg_user_mr+0xf8/0x190 [hns_roce_hw_v2] ib_uverbs_reg_mr+0x118/0x290 watchdog: BUG: soft lockup - CPU#35 stuck for 23s! ... Call trace: hns_roce_hem_list_find_mtt+0x7c/0xb0 [hns_roce_hw_v2] mtr_map_bufs+0xc4/0x204 [hns_roce_hw_v2] hns_roce_mtr_create+0x31c/0x3c4 [hns_roce_hw_v2] alloc_mr_pbl+0xb0/0x160 [hns_roce_hw_v2] hns_roce_reg_user_mr+0x108/0x1c0 [hns_roce_hw_v2] ib_uverbs_reg_mr+0x120/0x2bc Add a cond_resched() to fix soft lockup during these loops. In order not to affect the allocation performance of normal-size buffer, set the loop count of a 100GB MR as the threshold to call cond_resched().

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can make a CPU appear stuck when the HNS RoCE RDMA driver handles very large memory registrations. The business impact is availability risk on specialized servers using that hardware and driver, not broad internet exposure based on the supplied evidence.

Executive priority

Treat this as a targeted availability issue. It should be prioritized for RDMA-enabled infrastructure, HPC, storage, or virtualization hosts using HNS RoCE, but it is not supported as an actively exploited emergency in the supplied sources.

Technical view

The RDMA/hns driver loops while allocating and mapping buffer-table pages for very large memory regions, such as over 100GB. Without rescheduling inside the loop, the kernel watchdog can report soft lockups in hns_roce paths reached through ib_uverbs_reg_mr. Stable kernel commits add cond_resched() at a threshold.

Likely exposure

Exposure is likely limited to Linux systems using the hns_roce/HNS RDMA driver and workloads that register very large memory regions. General Linux servers without this RDMA hardware or driver path are less likely to be affected.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit tooling. The demonstrated condition is a soft lockup during large MR allocation and mapping, which points primarily to denial-of-service or reliability impact.

Researcher notes

The source bundle lacks CVSS, CWE, and detailed version-range semantics. Analysis should center on driver reachability, kernel provenance, and whether untrusted or tenant-controlled workloads can trigger large RDMA memory registrations.

Mitigation direction

  • Apply vendor or stable kernel updates containing the referenced RDMA/hns fixes.
  • Debian users should review the listed LTS advisories and update affected kernel packages.
  • Prioritize hosts using HNS RoCE RDMA hardware or very large memory registrations.
  • If patching is delayed, consult vendor guidance before relying on operational workarounds.

Validation and detection

  • Inventory Linux hosts using the hns_roce or HNS RDMA driver.
  • Map running kernel builds to vendor advisories or the referenced stable commits.
  • Check system logs for watchdog soft lockups with hns_roce or ib_uverbs_reg_mr traces.
  • Confirm updated kernels include the RDMA/hns cond_resched() fix.
Prepared
Confidence
medium
Sources
11

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-22010 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
1ADP providers
10Source 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.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux38389eaa4db192648916464b60f6086d6bbaa6de, 38389eaa4db192648916464b60f6086d6bbaa6de, 38389eaa4db192648916464b60f6086d6bbaa6de, 38389eaa4db192648916464b60f6086d6bbaa6de, 38389eaa4db192648916464b60f6086d6bbaa6de, 38389eaa4db192648916464b60f6086d6bbaa6de, 38389eaa4db192648916464b60f6086d6bbaa6deunaffected
LinuxLinux5.3, 0, 5.10.236, 5.15.180, 6.1.132, 6.6.85, 6.12.21, 6.13.9, 6.14affected
Weakness

CWE details

No CWE listed

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