Answer in brief
CVE-2026-46265 records a Unknown severity vulnerability in RDMA/hns: Fix WQ_MEM_RECLAIM warning. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <12761bd0ae16a80f237c2a65ab1b1064076cc74a || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <70a5eb757ace5bd627a36f04d871eaf85def424d || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <562c96b1393da2df3ea62173c84117b39da353b9 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c5ef9a1bcf5b597695d9c2e6ac452e9f89521862 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f6 | 12761bd0ae16a80f237c2a65ab1b1064076cc74a, 70a5eb757ace5bd627a36f04d871eaf85def424d, 562c96b1393da2df3ea62173c84117b39da353b9, 0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27, c5ef9a1bcf5b597695d9c2e6ac452e9f89521862, c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f6 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Jun 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46265 records a Unknown severity vulnerability in RDMA/hns: Fix WQ_MEM_RECLAIM warning. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <12761bd0ae16a80f237c2a65ab1b1064076cc74a || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <70a5eb757ace5bd627a36f04d871eaf85def424d || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <562c96b1393da2df3ea62173c84117b39da353b9 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c5ef9a1bcf5b597695d9c2e6ac452e9f89521862 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f6 | 12761bd0ae16a80f237c2a65ab1b1064076cc74a, 70a5eb757ace5bd627a36f04d871eaf85def424d, 562c96b1393da2df3ea62173c84117b39da353b9, 0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27, c5ef9a1bcf5b597695d9c2e6ac452e9f89521862, c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f6 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Jun 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.