HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 46265 rdmahns fix wqmemreclaim warning
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Contribute to HOL
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 7.5CVE-2026-46265

RDMA/hns: Fix WQ_MEM_RECLAIM warningCVE-2026-46265

Answer in brief

CVE-2026-46265 records a High severity (CVSS 7.5) 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), 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.

Published Jun 3, 2026Updated Oct 30, 2026Source checked Nov 5, 2026First seen by HOL Aug 5, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
NVD-CWE-noinfo
Source
CVE List V5
Source checked
Nov 5, 2026
References
8 linked sources
Open source record

Key facts

Risk
High · CVSS 7.5
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.5. 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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=ffd541d45726341c1830ff595fd7352b6d1cfbcd <12761bd0ae16a80f237c2a65ab1b1064076cc74a || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <70a5eb757ace5bd627a36f04d871eaf85def424d || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <562c96b1393da2df3ea62173c84117b39da353b9 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c5ef9a1bcf5b597695d9c2e6ac452e9f89521862 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f612761bd0ae16a80f237c2a65ab1b1064076cc74a, 70a5eb757ace5bd627a36f04d871eaf85def424d, 562c96b1393da2df3ea62173c84117b39da353b9, 0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27, c5ef9a1bcf5b597695d9c2e6ac452e9f89521862, c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f6
Linux/Linuxgeneric5.7Not reported
Linux/Linuxgeneric>=ffd541d45726341c1830ff595fd7352b6d1cfbcd <31b22ca4f5ab8c495fd8bb44c06573f1fb7833a2 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <5fb5028a7a80c2f8fd1e06cea7c4a0af1a58f9ef || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <12761bd0ae16a80f237c2a65ab1b1064076cc74a || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <70a5eb757ace5bd627a36f04d871eaf85def424d || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <562c96b1393da2df3ea62173c84117b39da353b9 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c5ef9a1bcf5b597695d9c2e6ac452e9f89521862 || >=ffd541d45726341c1830ff595fd7352b6d1cfbcd <c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f631b22ca4f5ab8c495fd8bb44c06573f1fb7833a2, 5fb5028a7a80c2f8fd1e06cea7c4a0af1a58f9ef, 12761bd0ae16a80f237c2a65ab1b1064076cc74a, 70a5eb757ace5bd627a36f04d871eaf85def424d, 562c96b1393da2df3ea62173c84117b39da353b9, 0cbec8b49270f3f0600b8e3ef5e8f0d233dcea27, c5ef9a1bcf5b597695d9c2e6ac452e9f89521862, c0a26bbd3f99b7b03f072e3409aff4e6ec8af6f6

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 12761bd0ae16a80f237c2a65ab1b1064076cc74a; Linux/Linux to 31b22ca4f5ab8c495fd8bb44c06573f1fb7833a2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 3, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 30, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 5, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source 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.

Quoted source text, attributed separately from HOL analysis.