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.
  • CIGARPoint your coding agent at the right lines and cut its token bill by about a third.

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.
  • Gauntlet benchmarkGuard tested with real coding agents: safe work runs, risky actions stop.

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 68404 wifi cfg80211 use wiphy work for socket owner
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

Get HOL Guard for your computer

HOL Guard is a free desktop app that watches what coding agents such as Claude Code, Codex and Cursor run, read and install, and asks you before anything risky happens.

  • Download for macOS
  • Windows download
  • Linux download

Free. macOS 13+ on Apple silicon, Windows x64, Linux AppImage. Other ways to install

Runs on
macOS 13 or later on Apple silicon, Windows x64 and Linux x86_64.
Price
Free. Paid plans add Guard Cloud for teams. See pricing
Where your data stays
On your computer. Guard Cloud is optional.
Token savings
33% to 38% lower spend across three coding agents in our CIGAR benchmark.

HOL

HOL builds open infrastructure for AI agents: HOL Guard, a directory of AI plugins and MCP servers, an AI agent registry and the open HCS standards.

  • GitHub (opens in a new tab)
  • X (Twitter) (opens in a new tab)
  • YouTube (opens in a new tab)
  • Telegram (opens in a new tab)

HOL Guard

  • What is HOL Guard
  • Features
  • Cut coding agent token costs (CIGAR)
  • Install Guard
  • Download the desktop app
  • Pricing
  • Guard for teams
  • Compare Guard
  • Release notes

Guard for your AI tool

  • Guard for Claude Code
  • Guard for Codex
  • Guard for Cursor
  • Guard for GitHub Copilot CLI
  • Guard for OpenCode
  • Guard for Pi and Oh My Pi
  • Guard for Hermes
  • Guard for OpenClaw
  • All supported AI tools

Research and security

  • Gauntlet: Guard tested with real agents
  • CIGAR token benchmark
  • Research
  • AI security hub
  • Security advisories
  • Active CVEs in AI tools
  • AI agent security guides
  • Extensions and coverage

Plugins and MCP servers

  • Browse AI plugins
  • New 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

AI agent registry

  • Best AI agents
  • Best ERC-8004 agents
  • Best Virtuals agents
  • Best A2A agents
  • Best x402 payable agents
  • Submit an ERC-8004 contract
  • Feature your agent

Developers

  • Guard docs
  • Documentation index
  • Developer hub
  • Registry API reference
  • OpenAPI spec
  • Registry OpenAPI spec
  • Run in Postman (opens in a new tab)
  • HCS standards

Company

  • About HOL
  • Blog
  • Contribute to HOL
  • Guard contributors
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact

Copyright © 2026 HOL DAO LLC. All rights reserved.

  • Privacy
  • Terms of Service
Back to active CVEs
High · CVSS 7.8CVE-2026-68404

wifi: cfg80211: use wiphy work for socket owner autodisconnectCVE-2026-68404

Answer in brief

CVE-2026-68404 records a High severity (CVSS 7.8) vulnerability in wifi: cfg80211: use wiphy work for socket owner autodisconnect. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 10, 2026Updated Oct 30, 2026Source checked Nov 9, 2026First seen by HOL Aug 10, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-662
Source
CVE List V5
Source checked
Nov 9, 2026
References
6 linked sources
Open source record

Key facts

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

Why this deserves its current priority

CVSS is 7.8. 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), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=bd2522b168847106c1885f0319a2833bdf88bf9a <6d6123fef5a4af175cc6b6b12a03dd0f3c240b79 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <0c2ed186bbe14304415476d6707b747dddcd85836d6123fef5a4af175cc6b6b12a03dd0f3c240b79, 0c2ed186bbe14304415476d6707b747dddcd8583
Linux/Linuxgeneric4.11Not reported
Linux/Linuxgeneric>=bd2522b168847106c1885f0319a2833bdf88bf9a <c2ddd180bbee766cf7359473d623423ea9485d93 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <6d6123fef5a4af175cc6b6b12a03dd0f3c240b79 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <0c2ed186bbe14304415476d6707b747dddcd8583c2ddd180bbee766cf7359473d623423ea9485d93, 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79, 0c2ed186bbe14304415476d6707b747dddcd8583
Linux/Linuxgeneric>=bd2522b168847106c1885f0319a2833bdf88bf9a <c55590e4c69e0fd194df6d20bc35381c201d99e1 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <4087a9ba4ece70297a4174afaa41c0b700302b65 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <c2ddd180bbee766cf7359473d623423ea9485d93 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <6d6123fef5a4af175cc6b6b12a03dd0f3c240b79 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <0c2ed186bbe14304415476d6707b747dddcd8583c55590e4c69e0fd194df6d20bc35381c201d99e1, 4087a9ba4ece70297a4174afaa41c0b700302b65, c2ddd180bbee766cf7359473d623423ea9485d93, 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79, 0c2ed186bbe14304415476d6707b747dddcd8583
Linux/Linuxgeneric>=bd2522b168847106c1885f0319a2833bdf88bf9a <23517673b1eecaec95e61dde285220d5a980cf3f || >=bd2522b168847106c1885f0319a2833bdf88bf9a <c55590e4c69e0fd194df6d20bc35381c201d99e1 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <4087a9ba4ece70297a4174afaa41c0b700302b65 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <c2ddd180bbee766cf7359473d623423ea9485d93 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <6d6123fef5a4af175cc6b6b12a03dd0f3c240b79 || >=bd2522b168847106c1885f0319a2833bdf88bf9a <0c2ed186bbe14304415476d6707b747dddcd858323517673b1eecaec95e61dde285220d5a980cf3f, c55590e4c69e0fd194df6d20bc35381c201d99e1, 4087a9ba4ece70297a4174afaa41c0b700302b65, c2ddd180bbee766cf7359473d623423ea9485d93, 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79, 0c2ed186bbe14304415476d6707b747dddcd8583

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 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79; Linux/Linux to c2ddd180bbee766cf7359473d623423ea9485d93; Linux/Linux to c55590e4c69e0fd194df6d20bc35381c201d99e1; Linux/Linux to 23517673b1eecaec95e61dde285220d5a980cf3f if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 10, 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 10, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: use wiphy work for socket owner autodisconnect nl80211_netlink_notify() walks the cfg80211 wireless device list when a NETLINK_GENERIC socket is released. If the socket owns a connection, the notifier queues the embedded wdev->disconnect_wk work item. That work is a plain work_struct today. NETDEV_GOING_DOWN cancels it, but a NETLINK_URELEASE notifier that already observed conn_owner_nlportid can queue it after that cancel returns. _cfg80211_unregister_wdev() then removes the wdev from the list and waits for RCU readers, but synchronize_net() does not drain work queued by such a reader. Make the autodisconnect work a wiphy_work instead. The callback already needs the wiphy mutex, and wiphy_work runs under that mutex. This lets teardown cancel pending autodisconnect work while holding the mutex, without a cancel_work_sync() vs. worker locking concern. Also cancel the wiphy work after list_del_rcu() and synchronize_net(). Any NETLINK_URELEASE notifier that had already reached the wdev list has then either queued the work and it is removed, or can no longer find the wdev.

Quoted source text, attributed separately from HOL analysis.