CVE-2025-38582: RDMA/hns: Fix double destruction of rsv_qp
In the Linux kernel, the following vulnerability has been resolved:
RDMA/hns: Fix double destruction of rsv_qp
rsv_qp may be double destroyed in error flow, first in free_mr_init(),
and then in hns_roce_exit(). Fix it by moving the free_mr_init() call
into hns_roce_v2_init().
list_del corruption, ffff589732eb9b50->next is LIST_POISON1 (dead000000000100)
WARNING: CPU: 8 PID: 1047115 at lib/list_debug.c:53 __list_del_entry_valid+0x148/0x240
...
Call trace:
__list_del_entry_valid+0x148/0x240
hns_roce_qp_remove+0x4c/0x3f0 [hns_roce_hw_v2]
hns_roce_v2_destroy_qp_common+0x1dc/0x5f4 [hns_roce_hw_v2]
hns_roce_v2_destroy_qp+0x22c/0x46c [hns_roce_hw_v2]
free_mr_exit+0x6c/0x120 [hns_roce_hw_v2]
hns_roce_v2_exit+0x170/0x200 [hns_roce_hw_v2]
hns_roce_exit+0x118/0x350 [hns_roce_hw_v2]
__hns_roce_hw_v2_init_instance+0x1c8/0x304 [hns_roce_hw_v2]
hns_roce_hw_v2_reset_notify_init+0x170/0x21c [hns_roce_hw_v2]
hns_roce_hw_v2_reset_notify+0x6c/0x190 [hns_roce_hw_v2]
hclge_notify_roce_client+0x6c/0x160 [hclge]
hclge_reset_rebuild+0x150/0x5c0 [hclge]
hclge_reset+0x10c/0x140 [hclge]
hclge_reset_subtask+0x80/0x104 [hclge]
hclge_reset_service_task+0x168/0x3ac [hclge]
hclge_service_task+0x50/0x100 [hclge]
process_one_work+0x250/0x9a0
worker_thread+0x324/0x990
kthread+0x190/0x210
ret_from_fork+0x10/0x18
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver bug in the RDMA/hns RoCE path. During a reset or initialization error path, the same reserved queue pair can be destroyed twice, corrupting kernel list state. The public record does not provide CVSS, confirmed exploitation, or a detailed impact statement.
Executive priority
Track this for normal kernel patch management, with higher priority for hosts using the affected RDMA/hns driver. The current public evidence does not support emergency treatment, but kernel reliability issues on infrastructure hosts can still affect service availability.
Technical view
CVE-2025-38582 resolves double destruction of rsv_qp in RDMA/hns. The trace shows list_del corruption in hns_roce_qp_remove during hns_roce_v2_exit after reset notification handling. The fix moves free_mr_init() into hns_roce_v2_init() to avoid free_mr_init() and hns_roce_exit() both destroying the resource.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the hns RoCE RDMA driver path in use. Systems without this driver, hardware path, or affected kernel lineage are less likely exposed. The CVE record lists default status as unaffected except specified affected versions.
Exploitation context
The source bundle states KEV is false and provides no evidence of active exploitation. The observed failure is an error/reset flow causing kernel list corruption. Treat this primarily as a reliability and availability risk unless vendor advisories provide more impact detail.
Researcher notes
The record is precise about root cause and fix location but incomplete on impact scoring. Validation should focus on affected kernel lineage and whether the RDMA/hns driver path is present. Do not assume remote exploitability from the available evidence.
Mitigation direction
Apply vendor-supported Linux kernel updates containing the referenced stable fixes.
Prioritize hosts using RDMA/hns or hns_roce_hw_v2 functionality.
If patching is delayed, check vendor guidance for supported workarounds.
Avoid direct wrangling of kernel fixes outside normal distribution channels.
Validation and detection
Inventory kernel versions against the CVE affected-version ranges.
Check whether hns_roce_hw_v2 or related RDMA/hns modules are loaded.
Review kernel logs for reset-flow list corruption involving hns_roce.
Confirm the deployed kernel includes one of the referenced stable commits.
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-38582 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Aug 19, 2025, 17:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.