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 64036 cgrouprstat validate cpu before cssrstatcpu access
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-2026-64036

cgroup/rstat: validate cpu before css_rstat_cpu() accessCVE-2026-64036

Answer in brief

CVE-2026-64036 records a High severity (CVSS 7.8) vulnerability in cgroup/rstat: validate cpu before css_rstat_cpu() access. 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). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 19, 2026Updated Oct 30, 2026Source checked Nov 4, 2026First seen by HOL Aug 5, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

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

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
9 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). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=a319185be9f5ad13c2a296d448ac52ffe45d194c <6a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <fd2bd9fa7700ddf28296486b2598cff2f80cc819 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <8817005efbdfdf5d4e4814cb5dc52b53d12917d76a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6, fd2bd9fa7700ddf28296486b2598cff2f80cc819, 8817005efbdfdf5d4e4814cb5dc52b53d12917d7
Linux/Linuxgeneric6.1Not reported
Linux/Linuxgeneric>=a319185be9f5ad13c2a296d448ac52ffe45d194c <b28b862b07257219755d0b0a7fbe5d23b7c9ea91 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <3d595affbe00a2e8bf43b9f2947a8efcdc1c059e || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <6a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <fd2bd9fa7700ddf28296486b2598cff2f80cc819 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <8817005efbdfdf5d4e4814cb5dc52b53d12917d7b28b862b07257219755d0b0a7fbe5d23b7c9ea91, 3d595affbe00a2e8bf43b9f2947a8efcdc1c059e, 6a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6, fd2bd9fa7700ddf28296486b2598cff2f80cc819, 8817005efbdfdf5d4e4814cb5dc52b53d12917d7
Linux/Linuxgeneric>=a319185be9f5ad13c2a296d448ac52ffe45d194c <ee5afb74688aa6f1f16d8c7e7b6bfaf803fb62fc || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <b28b862b07257219755d0b0a7fbe5d23b7c9ea91 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <3d595affbe00a2e8bf43b9f2947a8efcdc1c059e || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <6a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <fd2bd9fa7700ddf28296486b2598cff2f80cc819 || >=a319185be9f5ad13c2a296d448ac52ffe45d194c <8817005efbdfdf5d4e4814cb5dc52b53d12917d7ee5afb74688aa6f1f16d8c7e7b6bfaf803fb62fc, b28b862b07257219755d0b0a7fbe5d23b7c9ea91, 3d595affbe00a2e8bf43b9f2947a8efcdc1c059e, 6a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6, fd2bd9fa7700ddf28296486b2598cff2f80cc819, 8817005efbdfdf5d4e4814cb5dc52b53d12917d7

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 6a01413a4e8fcb0263d7bef5075c5f8f4eb3a8b6; Linux/Linux to b28b862b07257219755d0b0a7fbe5d23b7c9ea91; Linux/Linux to ee5afb74688aa6f1f16d8c7e7b6bfaf803fb62fc if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jul 19, 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 5, 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: cgroup/rstat: validate cpu before css_rstat_cpu() access css_rstat_updated() is exposed as a BPF kfunc and accepts a caller-provided cpu argument. The function uses cpu for per-cpu rstat lookups without checking whether it refers to a valid possible CPU. A BPF iter/cgroup program with CAP_BPF and CAP_PERFMON can pass an invalid cpu value. On an unfixed UBSCAN_BOUNDS test kernel, cpu == 0x7fffffff triggers: UBSAN: array-index-out-of-bounds in kernel/cgroup/rstat.c:31:9 index 2147483647 is out of range for type 'long unsigned int [64]' Call Trace: css_rstat_updated bpf_iter_run_prog cgroup_iter_seq_show bpf_seq_read Add cpu validation to the BPF-facing css_rstat_updated() kfunc and move the common implementation to __css_rstat_updated() for in-kernel callers.

Quoted source text, attributed separately from HOL analysis.