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 93125 bpf reject rdonlyrdwrbufsize kfunc arguments that
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
  • 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.8CVE-2026-93125

bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 maxCVE-2026-93125

Answer in brief

CVE-2026-93125 records a High severity (CVSS 7.8) vulnerability in bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max. 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 Sep 17, 2026Updated Oct 30, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 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 1, 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>=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <56a3846830ac95a472297d0cbba75cbff29540bb || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <2aaf67f0516fde29620d0edfc29c01b9ea7ad43056a3846830ac95a472297d0cbba75cbff29540bb, 2aaf67f0516fde29620d0edfc29c01b9ea7ad430
Linux/Linuxgeneric6.1Not reported
Linux/Linuxgeneric>=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <93a20b14f8627b2d3486e3ec1d3f2e7275a506ec || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <56a3846830ac95a472297d0cbba75cbff29540bb || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <2aaf67f0516fde29620d0edfc29c01b9ea7ad43093a20b14f8627b2d3486e3ec1d3f2e7275a506ec, 56a3846830ac95a472297d0cbba75cbff29540bb, 2aaf67f0516fde29620d0edfc29c01b9ea7ad430
Linux/Linuxgeneric>=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <2147065d3a4e1d5d42ae553fef165f17ec5e0e79 || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <b6ac0b5732047d43172b9dfbe6b57b9b8de303c2 || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <93a20b14f8627b2d3486e3ec1d3f2e7275a506ec || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <56a3846830ac95a472297d0cbba75cbff29540bb || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <2aaf67f0516fde29620d0edfc29c01b9ea7ad4302147065d3a4e1d5d42ae553fef165f17ec5e0e79, b6ac0b5732047d43172b9dfbe6b57b9b8de303c2, 93a20b14f8627b2d3486e3ec1d3f2e7275a506ec, 56a3846830ac95a472297d0cbba75cbff29540bb, 2aaf67f0516fde29620d0edfc29c01b9ea7ad430
Linux/Linuxgeneric>=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <00bb52be60da16cd5ead4eb9f8ddc9a66d003ff2 || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <2147065d3a4e1d5d42ae553fef165f17ec5e0e79 || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <b6ac0b5732047d43172b9dfbe6b57b9b8de303c2 || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <93a20b14f8627b2d3486e3ec1d3f2e7275a506ec || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <56a3846830ac95a472297d0cbba75cbff29540bb || >=eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae <2aaf67f0516fde29620d0edfc29c01b9ea7ad43000bb52be60da16cd5ead4eb9f8ddc9a66d003ff2, 2147065d3a4e1d5d42ae553fef165f17ec5e0e79, b6ac0b5732047d43172b9dfbe6b57b9b8de303c2, 93a20b14f8627b2d3486e3ec1d3f2e7275a506ec, 56a3846830ac95a472297d0cbba75cbff29540bb, 2aaf67f0516fde29620d0edfc29c01b9ea7ad430

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 56a3846830ac95a472297d0cbba75cbff29540bb; Linux/Linux to 93a20b14f8627b2d3486e3ec1d3f2e7275a506ec; Linux/Linux to 2147065d3a4e1d5d42ae553fef165f17ec5e0e79; Linux/Linux to 00bb52be60da16cd5ead4eb9f8ddc9a66d003ff2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 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

    Sep 17, 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: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max check_kfunc_args() detects a kfunc argument named rdonly_buf_size or rdwr_buf_size and stores reg->var_off.value into meta->r0_size, a u64, and does not bound it. check_kfunc_call() later copies that value into the returned register's mem_size field: meta->r0_size = reg->var_off.value; ... regs[BPF_REG_0].mem_size = meta.r0_size; regs[BPF_REG_0].mem_size is u32. A constant whose upper 32 bits are set gets truncated instead of causing a load-time rejection, so the verifier records a PTR_TO_MEM register with an approximately 4 GiB mem_size for whatever allocation the kfunc returned. A later access check against that register uses the truncated, wrong bound. Reject rdonly_buf_size/rdwr_buf_size values that exceed U32_MAX at the point meta->r0_size is set.

Quoted source text, attributed separately from HOL analysis.