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 74269 bnxt fix head underflow on xdp head grow
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
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
Critical · CVSS 9.8CVE-2026-74269

bnxt: fix head underflow on XDP head-growCVE-2026-74269

Answer in brief

CVE-2026-74269 records a Critical severity (CVSS 9.8) vulnerability in bnxt: fix head underflow on XDP head-grow. 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 15, 2026Updated Oct 30, 2026Source checked Nov 13, 2026First seen by HOL Aug 15, 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 13, 2026
References
6 linked sources
Open source record

Key facts

Risk
Critical · CVSS 9.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 9.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>=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <bb72b1c6755631c74b7e0878ee55bb81c06776c0 || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <e26657fe3b85c068b01f42bb0c602f242d643ba9 || e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16 || ae0e135dc900827687ecc684c2bbb57aae48d318 || >=6.1.45 <6.2 || >=6.4.10 <6.5bb72b1c6755631c74b7e0878ee55bb81c06776c0, e26657fe3b85c068b01f42bb0c602f242d643ba9, 6.2, 6.5
Linux/Linuxgeneric6.5Not reported
Linux/Linuxgeneric>=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <4c03275bc4435cc8e25f7f3f08aff58c0e783d8d || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <bb72b1c6755631c74b7e0878ee55bb81c06776c0 || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <e26657fe3b85c068b01f42bb0c602f242d643ba9 || e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16 || ae0e135dc900827687ecc684c2bbb57aae48d318 || >=6.1.45 <6.2 || >=6.4.10 <6.54c03275bc4435cc8e25f7f3f08aff58c0e783d8d, bb72b1c6755631c74b7e0878ee55bb81c06776c0, e26657fe3b85c068b01f42bb0c602f242d643ba9, 6.2, 6.5
Linux/Linuxgeneric>=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <3e8f3959a7fd28461b8cd9708c21286b4250b77a || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <ff34e5a26a26c92142afea11455e259c4c4c617b || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <4c03275bc4435cc8e25f7f3f08aff58c0e783d8d || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <bb72b1c6755631c74b7e0878ee55bb81c06776c0 || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <e26657fe3b85c068b01f42bb0c602f242d643ba9 || e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16 || ae0e135dc900827687ecc684c2bbb57aae48d318 || >=6.1.45 <6.2 || >=6.4.10 <6.53e8f3959a7fd28461b8cd9708c21286b4250b77a, ff34e5a26a26c92142afea11455e259c4c4c617b, 4c03275bc4435cc8e25f7f3f08aff58c0e783d8d, bb72b1c6755631c74b7e0878ee55bb81c06776c0, e26657fe3b85c068b01f42bb0c602f242d643ba9, 6.2, 6.5
Linux/Linuxgeneric>=e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16 <59f6211c006cb5936b443fb396eb43864ca21ed5 || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <3e8f3959a7fd28461b8cd9708c21286b4250b77a || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <ff34e5a26a26c92142afea11455e259c4c4c617b || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <4c03275bc4435cc8e25f7f3f08aff58c0e783d8d || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <bb72b1c6755631c74b7e0878ee55bb81c06776c0 || >=f6974b4c2d8e1062b5a52228ee47293c15b4ee1e <e26657fe3b85c068b01f42bb0c602f242d643ba9 || ae0e135dc900827687ecc684c2bbb57aae48d318 || >=6.1.45 <6.1.191 || >=6.4.10 <6.559f6211c006cb5936b443fb396eb43864ca21ed5, 3e8f3959a7fd28461b8cd9708c21286b4250b77a, ff34e5a26a26c92142afea11455e259c4c4c617b, 4c03275bc4435cc8e25f7f3f08aff58c0e783d8d, bb72b1c6755631c74b7e0878ee55bb81c06776c0, e26657fe3b85c068b01f42bb0c602f242d643ba9, 6.1.191, 6.5

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 bb72b1c6755631c74b7e0878ee55bb81c06776c0; Linux/Linux to 4c03275bc4435cc8e25f7f3f08aff58c0e783d8d; Linux/Linux to 3e8f3959a7fd28461b8cd9708c21286b4250b77a; Linux/Linux to 59f6211c006cb5936b443fb396eb43864ca21ed5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 15, 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 15, 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: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is < 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is >= 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.

Quoted source text, attributed separately from HOL analysis.