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 93105 esp do not unref managed frag pages in espssgunref
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-93105

esp: do not unref managed frag pages in esp_ssg_unref()CVE-2026-93105

Answer in brief

CVE-2026-93105 records a High severity (CVSS 7.8) vulnerability in esp: do not unref managed frag pages in esp_ssg_unref(). 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>=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <21697720ff43b8dfa25b8e8d9ca7f56f4597fc8026b6b14c7a0368e317a1e9fb5144ebe6f8d495cf, 21697720ff43b8dfa25b8e8d9ca7f56f4597fc80
Linux/Linuxgeneric4.11Not reported
Linux/Linuxgeneric>=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <1ad6456898f6e6cf58be83bdb607acb1119a9cd1 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <21697720ff43b8dfa25b8e8d9ca7f56f4597fc801ad6456898f6e6cf58be83bdb607acb1119a9cd1, 26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf, 21697720ff43b8dfa25b8e8d9ca7f56f4597fc80
Linux/Linuxgeneric>=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <201bdf10ae92e7cbd524adf8c0323e2a963d5fd7 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <3ec55f0c8a6a543cf660584d1346e11f6311ee59 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <1ad6456898f6e6cf58be83bdb607acb1119a9cd1 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <21697720ff43b8dfa25b8e8d9ca7f56f4597fc80201bdf10ae92e7cbd524adf8c0323e2a963d5fd7, 3ec55f0c8a6a543cf660584d1346e11f6311ee59, 1ad6456898f6e6cf58be83bdb607acb1119a9cd1, 26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf, 21697720ff43b8dfa25b8e8d9ca7f56f4597fc80
Linux/Linuxgeneric>=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <cb375965800d474c0281a2e92c43c724fce9f463 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <201bdf10ae92e7cbd524adf8c0323e2a963d5fd7 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <3ec55f0c8a6a543cf660584d1346e11f6311ee59 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <1ad6456898f6e6cf58be83bdb607acb1119a9cd1 || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf || >=cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <21697720ff43b8dfa25b8e8d9ca7f56f4597fc80cb375965800d474c0281a2e92c43c724fce9f463, 201bdf10ae92e7cbd524adf8c0323e2a963d5fd7, 3ec55f0c8a6a543cf660584d1346e11f6311ee59, 1ad6456898f6e6cf58be83bdb607acb1119a9cd1, 26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf, 21697720ff43b8dfa25b8e8d9ca7f56f4597fc80

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 26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf; Linux/Linux to 1ad6456898f6e6cf58be83bdb607acb1119a9cd1; Linux/Linux to 201bdf10ae92e7cbd524adf8c0323e2a963d5fd7; Linux/Linux to cb375965800d474c0281a2e92c43c724fce9f463 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: esp: do not unref managed frag pages in esp_ssg_unref() esp_ssg_unref() releases the page references held on the source scatterlist after the AEAD operation completes. It calls skb_page_unref() on every frag page for an out-of-place transform (req->src != req->dst), and in the error path of esp_output_tail() (already_unref == true) on the request's own scatterlist. This is wrong when the skb carries managed frags (SKBFL_MANAGED_FRAG_REFS). Managed frags are owned by a zerocopy ubuf and the skb does not hold a per-frag page reference; io_uring SEND_ZC with a registered buffer attaches the bvec pages this way via io_sg_from_iter(). The rest of the stack honours this invariant: skb_release_data() skips the per-frag unref when SKBFL_MANAGED_FRAG_REFS is set, and skb_zcopy_managed() is the guard used at the other unref sites. esp_ssg_unref() is missing that guard, so for a managed-frag skb it drops a page reference the skb never acquired. This can underflow the page reference count and free a page that is still in use. Guard the function with skb_zcopy_managed() so both unref paths are skipped for managed-frag skbs, matching skb_release_data().

Quoted source text, attributed separately from HOL analysis.