CVE-2026-46265 Details
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix WQ_MEM_RECLAIM warning When sunrpc is used, if a reset triggered, our wq may lead the following trace: workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma] is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle [hns_roce_hw_v2] WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144 Call trace: check_flush_dependency+0xe0/0x144 start_flush_work.constprop.0+0x1d0/0x2f0 __flush_work.isra.0+0x40/0xb0 flush_work+0x14/0x30 hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2] ib_destroy_qp_user+0x9c/0x2b4 rdma_destroy_qp+0x34/0xb0 rpcrdma_ep_destroy+0x28/0xcc [rpcrdma] rpcrdma_ep_put+0x74/0xb4 [rpcrdma] rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma] xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma] process_one_work+0x1cc/0x4d0 worker_thread+0x154/0x414 kthread+0x104/0x144 ret_from_fork+0x10/0x18 Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.
A warning related to workqueue memory reclamation has been addressed in the Linux kernel's RDMA/hns component. When the sunrpc protocol is used and a reset occurs, the workqueue may improperly flush work, leading to a warning. This issue arises because the destruction of a Queue Pair (QP) frees memory, but the associated workqueue is not correctly marked for memory reclamation. The warning indicates a potential problem in the workqueue management, which could lead to improper handling of resources.
The vulnerability has been fixed in the Linux kernel. Users can upgrade to the latest version of the stable Linux kernel to address this issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27 | kernel.org | Patch |
| https://git.kernel.org/stable/c/12761bd0ae16a80f237c2a65ab1b1064076cc74a | kernel.org | Patch |
| https://git.kernel.org/stable/c/562c96b1393da2df3ea62173c84117b39da353b9 | kernel.org | Patch |
| https://git.kernel.org/stable/c/70a5eb757ace5bd627a36f04d871eaf85def424d | kernel.org | Patch |
| https://git.kernel.org/stable/c/c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c5ef9a1bcf5b597695d9c2e6ac452e9f89521862 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.7, < 6.1.165 >= 6.2, < 6.6.128 >= 6.7, < 6.12.75 >= 6.13, < 6.18.14 >= 6.19, < 6.19.4 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 9, 2026 | Initial Analysis | [email protected] |
| Jun 5, 2026 | CVE Modified | kernel.org |
| Jun 3, 2026 | New CVE Received | kernel.org |