HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • AI 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

  • The ChallengePlay the night shift: judge your agent against the real 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 74715 bpf fix netns reference imbalance in conntrack
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

Star HOL Guard on GitHub to download
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
55.5% to 71.3% fewer tokens 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 Herdr 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)
  • AI standards · HOL Throughline
  • Compare AI standards
  • Collaboration ideas
  • HCS specifications

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-74715

bpf: Fix netns reference imbalance in conntrack kfuncsCVE-2026-74715

Answer in brief

CVE-2026-74715 records a High severity (CVSS 7.8) vulnerability in bpf: Fix netns reference imbalance in conntrack kfuncs. 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 22, 2026Updated Oct 30, 2026Source checked Nov 21, 2026First seen by HOL Aug 22, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Nov 21, 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>=aed8ee7feb44b6537af1e0b4f03365d42928be38 <e5e060eb63d10b41ab60fd955649479d99b38210 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <fdeba03fea78407a8c52faa99177c9f7f29f90ebe5e060eb63d10b41ab60fd955649479d99b38210, fdeba03fea78407a8c52faa99177c9f7f29f90eb
Linux/Linuxgeneric6.0Not reported
Linux/Linuxgeneric>=aed8ee7feb44b6537af1e0b4f03365d42928be38 <4af94462c0ca2187a02a1a6641020ae888c74d5c || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <e5e060eb63d10b41ab60fd955649479d99b38210 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <fdeba03fea78407a8c52faa99177c9f7f29f90eb4af94462c0ca2187a02a1a6641020ae888c74d5c, e5e060eb63d10b41ab60fd955649479d99b38210, fdeba03fea78407a8c52faa99177c9f7f29f90eb
Linux/Linuxgeneric>=aed8ee7feb44b6537af1e0b4f03365d42928be38 <fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <41731d4290400cb898f15f049ae4018d45415e69 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <4af94462c0ca2187a02a1a6641020ae888c74d5c || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <e5e060eb63d10b41ab60fd955649479d99b38210 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <fdeba03fea78407a8c52faa99177c9f7f29f90ebfb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8, 41731d4290400cb898f15f049ae4018d45415e69, 4af94462c0ca2187a02a1a6641020ae888c74d5c, e5e060eb63d10b41ab60fd955649479d99b38210, fdeba03fea78407a8c52faa99177c9f7f29f90eb
Linux/Linuxgeneric>=aed8ee7feb44b6537af1e0b4f03365d42928be38 <cfde990193135a35637e55f69e83e4ab441e60ab || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <41731d4290400cb898f15f049ae4018d45415e69 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <4af94462c0ca2187a02a1a6641020ae888c74d5c || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <e5e060eb63d10b41ab60fd955649479d99b38210 || >=aed8ee7feb44b6537af1e0b4f03365d42928be38 <fdeba03fea78407a8c52faa99177c9f7f29f90ebcfde990193135a35637e55f69e83e4ab441e60ab, fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8, 41731d4290400cb898f15f049ae4018d45415e69, 4af94462c0ca2187a02a1a6641020ae888c74d5c, e5e060eb63d10b41ab60fd955649479d99b38210, fdeba03fea78407a8c52faa99177c9f7f29f90eb

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 e5e060eb63d10b41ab60fd955649479d99b38210; Linux/Linux to 4af94462c0ca2187a02a1a6641020ae888c74d5c; Linux/Linux to fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8; Linux/Linux to cfde990193135a35637e55f69e83e4ab441e60ab if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 22, 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 22, 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: bpf: Fix netns reference imbalance in conntrack kfuncs The opts argument of the BPF conntrack kfuncs can point to a shared map value. __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read opts->netns_id separately when acquiring and releasing the network namespace reference. The reference imbalance can occur as follows: CPU 0 CPU 1 read opts->netns_id (-1) skip get_net_ns_by_id() write opts->netns_id (id) read opts->netns_id (id) put_net(net) /* no matching get */ The reverse transition leaks the reference. Repeating the unmatched put can destroy a live namespace and crash later users. The kernel reported: Oops: general protection fault, probably for non-canonical address KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef] RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700 Call Trace: __sys_bpf+0x1662/0x50c0 __x64_sys_bpf+0x73/0xb0 do_syscall_64+0xf9/0x540 entry_SYSCALL_64_after_hwframe+0x77/0x7f Kernel panic - not syncing: Fatal exception Snapshot every input field of opts with READ_ONCE() before validating or using it. The netns_id snapshot keeps the namespace get/put pair balanced, while the other snapshots keep the remaining options from changing partway through an invocation. The individual reads can still observe an inconsistent combination during a concurrent update, but each selected field value remains stable for that invocation.

Quoted source text, attributed separately from HOL analysis.