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 2025 38502 bpf fix oob access in cgroup local storage
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
  • Contribute to HOL
  • 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-2025-38502

bpf: Fix oob access in cgroup local storageCVE-2025-38502

Answer in brief

CVE-2025-38502 records a High severity (CVSS 7.8) vulnerability in bpf: Fix oob access in cgroup local storage. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). 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 16, 2025Updated Oct 15, 2026Source checked Nov 4, 2026First seen by HOL Aug 5, 2026Material review Oct 15, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
7 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), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:h:siemens:simatic_cn_4100:-:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:siemens:simatic_cn_4100_firmware:*:*:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=7d9c3427894fe70d1347b4820476bf37736d2ff0 <c1c74584b9b4043c52e41fec415226e582d266a3 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <66da7cee78590259b400e51a70622ccd41da7bb2 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <7acfa07c585e3d7a64654d38f0a5c762877d0b9b || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <41688d1fc5d163a6c2c0e95c0419e2cb31a44648 || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <19341d5c59e8c7e8528e40f8663e99d67810473c || >=7d9c3427894fe70d1347b4820476bf37736d2ff0 <abad3d0bad72a52137e0c350c59542d75ae4f513c1c74584b9b4043c52e41fec415226e582d266a3, 66da7cee78590259b400e51a70622ccd41da7bb2, 7acfa07c585e3d7a64654d38f0a5c762877d0b9b, 41688d1fc5d163a6c2c0e95c0419e2cb31a44648, 19341d5c59e8c7e8528e40f8663e99d67810473c, abad3d0bad72a52137e0c350c59542d75ae4f513
Linux/Linuxgeneric5.9Not reported
Siemens/SIMATIC CN 4100generic>=0 <V5.0V5.0

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Siemens/SIMATIC CN 4100.
  2. 2Review the reported fix. Update Linux/Linux to c1c74584b9b4043c52e41fec415226e582d266a3; Siemens/SIMATIC CN 4100 to V5.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 16, 2025

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 15, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 5, 2026

Sources and claim methodology

  • Source referencecert-portal.siemens.com
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencelists.debian.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix oob access in cgroup local storage Lonial reported that an out-of-bounds access in cgroup local storage can be crafted via tail calls. Given two programs each utilizing a cgroup local storage with a different value size, and one program doing a tail call into the other. The verifier will validate each of the indivial programs just fine. However, in the runtime context the bpf_cg_run_ctx holds an bpf_prog_array_item which contains the BPF program as well as any cgroup local storage flavor the program uses. Helpers such as bpf_get_local_storage() pick this up from the runtime context: ctx = container_of(current->bpf_ctx, struct bpf_cg_run_ctx, run_ctx); storage = ctx->prog_item->cgroup_storage[stype]; if (stype == BPF_CGROUP_STORAGE_SHARED) ptr = &READ_ONCE(storage->buf)->data[0]; else ptr = this_cpu_ptr(storage->percpu_buf); For the second program which was called from the originally attached one, this means bpf_get_local_storage() will pick up the former program's map, not its own. With mismatching sizes, this can result in an unintended out-of-bounds access. To fix this issue, we need to extend bpf_map_owner with an array of storage_cookie[] to match on i) the exact maps from the original program if the second program was using bpf_get_local_storage(), or ii) allow the tail call combination if the second program was not using any of the cgroup local storage maps.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Mongoose: Heap OOB reads and null-byte bypass in mg_path_is_sane (util.c)Also CWE-125
  • VeraCrypt: Heap overflow and out-of-bounds read in Serializable deserialization (elevated Core service input path)Also CWE-125

Record context

Vulnerability class
Buffer Overflow
EPSS
Not reported
CWE IDs
CWE-125
Source
CVE List V5
Source checked
Nov 4, 2026
References
8 linked sources
Open source record