RDMA/hns: Fix double destruction of rsv_qp
Affects the Linux kernel RDMA/hns driver in its driver-initialization error path. Fixed in stable releases 6.1.191, 6.6.160, 6.12.42, 6.15.10 and 6.16.1, depending on branch.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.1.191, 6.6.160, 6.11, 6.12, 6.12.42, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6.1.113 · fixed in 6.1.191; From 6.6.54 · fixed in 6.6.160; From 6.10.13 · fixed in 6.11; From 6.11.2 · fixed in 6.12
- Linux Linux
6.12
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.42; From 6.12.0 · fixed in 6.15.10; From 6.13.0 · fixed in 6.16.1
References 6
git.kernel.org
Questions about CVE-2025-38582
What does this mean?
During an error path in RDMA/hns driver initialization, the reserved queue pair rsv_qp can be destroyed twice. The fix stops that second destruction.Source: git.kernel.org
Am I affected, and how do I check?
The listed ranges cover Linux kernel 6.1.113 to before 6.1.191, 6.6.54 to before 6.6.160, 6.10.13 to before 6.11, 6.11.2 to before 6.12, and the kernel ranges from 6.7.0 to before 6.12.42, 6.12.0 to before 6.15.10, and 6.13.0 to before 6.16.1. To check a system, run uname -r and compare the version with these ranges, and run lsmod | grep hns to see whether the hns RDMA driver is loaded.Source: git.kernel.org
What should I do about it?
Update to a fixed stable kernel for your branch: 6.1.191, 6.6.160, 6.12.42, 6.15.10, 6.16.1, or later.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data