HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • AI 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

  • The ChallengePlay the night shift: judge your agent against the real 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 74632 mmhugememory fix hugezeropfn race
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
55.5% to 71.3% fewer tokens 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 Herdr 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)
  • AI standards · HOL Throughline
  • Compare AI standards
  • Collaboration ideas
  • HCS specifications

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
High · CVSS 7.8CVE-2026-74632

mm/huge_memory: fix huge_zero_pfn raceCVE-2026-74632

Answer in brief

CVE-2026-74632 records a High severity (CVSS 7.8) vulnerability in mm/huge_memory: fix huge_zero_pfn race. 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 Aug 22, 2026Updated Oct 24, 2026Source checked Nov 22, 2026First seen by HOL Aug 22, 2026Material review Oct 24, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Nov 22, 2026
References
8 linked sources
Open source record

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
4 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.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric5.13Not reported
Linux/Linuxgeneric>=3b77e8c8cde581dadab9a0f1543a347e24315f11 <6024f6d0d9b9ca5138bfc4ac6f6e4bdf616e42b3 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <105d04edbec83010df5728f74d17fd9c108e7553 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <ab7e4b407c7f58d1a003134eff3841f303d5ccc2 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <33192a26cddea7a7e4ca66e5c3eebd36fa8be2bb || fc1fbc5b017b6f5ef24a4a93f33cd022225e01c8 || bd092a0f19423d7e9e81182314a96ecd6a14f3b7 || 6527d8ef68c3ca3c455e38ae2a37cd7810caec73 || b1daf8f862136894a4595770a44e4508808fb806 || >=4.19.197 <4.20 || >=5.4.129 <5.5 || >=5.10.47 <5.11 || >=5.12.14 <5.136024f6d0d9b9ca5138bfc4ac6f6e4bdf616e42b3, 105d04edbec83010df5728f74d17fd9c108e7553, ab7e4b407c7f58d1a003134eff3841f303d5ccc2, 33192a26cddea7a7e4ca66e5c3eebd36fa8be2bb, 4.20, 5.5, 5.11, 5.13
Linux/Linuxgeneric>=3b77e8c8cde581dadab9a0f1543a347e24315f11 <9332b080ad57650d1dc582e54517f9fc78ef89cc || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <f3a874a903053c53fb53ba287ea9eacda69c68e8 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <6024f6d0d9b9ca5138bfc4ac6f6e4bdf616e42b3 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <105d04edbec83010df5728f74d17fd9c108e7553 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <ab7e4b407c7f58d1a003134eff3841f303d5ccc2 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <33192a26cddea7a7e4ca66e5c3eebd36fa8be2bb || fc1fbc5b017b6f5ef24a4a93f33cd022225e01c8 || bd092a0f19423d7e9e81182314a96ecd6a14f3b7 || 6527d8ef68c3ca3c455e38ae2a37cd7810caec73 || b1daf8f862136894a4595770a44e4508808fb806 || >=4.19.197 <4.20 || >=5.4.129 <5.5 || >=5.10.47 <5.11 || >=5.12.14 <5.139332b080ad57650d1dc582e54517f9fc78ef89cc, f3a874a903053c53fb53ba287ea9eacda69c68e8, 6024f6d0d9b9ca5138bfc4ac6f6e4bdf616e42b3, 105d04edbec83010df5728f74d17fd9c108e7553, ab7e4b407c7f58d1a003134eff3841f303d5ccc2, 33192a26cddea7a7e4ca66e5c3eebd36fa8be2bb, 4.20, 5.5, 5.11, 5.13
Linux/Linuxgeneric>=6527d8ef68c3ca3c455e38ae2a37cd7810caec73 <9c0fd1802ce06d7709f0bae4edeb085288f28764 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <b7041ba61c5da4e0b56f9be58cfb87d7689724e4 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <9332b080ad57650d1dc582e54517f9fc78ef89cc || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <f3a874a903053c53fb53ba287ea9eacda69c68e8 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <6024f6d0d9b9ca5138bfc4ac6f6e4bdf616e42b3 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <105d04edbec83010df5728f74d17fd9c108e7553 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <ab7e4b407c7f58d1a003134eff3841f303d5ccc2 || >=3b77e8c8cde581dadab9a0f1543a347e24315f11 <33192a26cddea7a7e4ca66e5c3eebd36fa8be2bb || fc1fbc5b017b6f5ef24a4a93f33cd022225e01c8 || bd092a0f19423d7e9e81182314a96ecd6a14f3b7 || b1daf8f862136894a4595770a44e4508808fb806 || >=5.10.47 <5.10.267 || >=4.19.197 <4.20 || >=5.4.129 <5.5 || >=5.12.14 <5.139c0fd1802ce06d7709f0bae4edeb085288f28764, b7041ba61c5da4e0b56f9be58cfb87d7689724e4, 9332b080ad57650d1dc582e54517f9fc78ef89cc, f3a874a903053c53fb53ba287ea9eacda69c68e8, 6024f6d0d9b9ca5138bfc4ac6f6e4bdf616e42b3, 105d04edbec83010df5728f74d17fd9c108e7553, ab7e4b407c7f58d1a003134eff3841f303d5ccc2, 33192a26cddea7a7e4ca66e5c3eebd36fa8be2bb, 5.10.267, 4.20, 5.5, 5.13

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 6024f6d0d9b9ca5138bfc4ac6f6e4bdf616e42b3; Linux/Linux to 9332b080ad57650d1dc582e54517f9fc78ef89cc; Linux/Linux to 9c0fd1802ce06d7709f0bae4edeb085288f28764 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 22, 2026

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

    Oct 24, 2026

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

    Aug 22, 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
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: fix huge_zero_pfn race Patch series "mm/huge_memory: fix huge_zero_pfn race", v2. There is a subtle race in the reference-counted huge_zero_folio implementation. The fast path atomic logic fails to account for the fact that the shrinker (which drops the final huge_zero_refcount pin) can overwrite huge_zero_pfn with the ~0UL sentinel value in shrink_huge_zero_folio_scan() after a racing get_huge_zero_folio() installed a valid value there. This results in huge_zero_folio being correctly set but huge_zero_pfn being set incorrectly and thus is_huge_zero_pfn() and consequently is_huge_zero_pmd() will misidentify the huge zero folio as being an ordinary THP folio. This can result in the huge zero folio being split and otherwise treated incorrectly. The solution to this is very subtle as there is an atomic fast path, and thus ordering in weakly ordered architectures has to be treated very carefully. The first commit fixes the issue by introducing a spinlock around huge_zero_[pfn, folio, refcount] write, with careful consideration paid to load/store ordering in the fast path. It is placed first and kept as small as possible so that it can be backported on its own. The second commit is a pure cleanup which reworks the CONFIG_PERSISTENT_HUGE_ZERO_FOLIO logic to better separate the persistent logic from the dynamically allocated one. This patch (of 2): If !CONFIG_PERSISTENT_HUGE_ZERO_FOLIO, the huge_zero_folio is refcounted by huge_zero_refcount and returned by mm_get_huge_zero_folio(). When the caller is done with the huge zero page, its reference count is decremented. Only a shrinker can set the reference count to zero. A race can unfortunately occur between a shrinker decrementing the reference count to zero and a concurrent page fault. This is because shrink_huge_zero_folio_scan() might, if very unlucky, be preempted between setting huge_zero_refcount to zero and writing an invalid value. During this time get_huge_zero_folio() could write to huge_zero_pfn before shrink_huge_zero_folio_scan() resumes. In this event the huge zero folio will be persistently misidentified causing the THP code path to be entered inappropriately for the huge zero folio: CPU 0 CPU 1 =======================================|================================= shrink_huge_zero_folio_scan() | atomic_cmpxchg() sets refcount to 0 | xchg() sets huge_zero_folio to NULL | get_huge_zero_folio() | | atomic_inc_not_zero() -> zero preempted for a long time | Allocate new huge zero folio | | Write valid huge_zero_folio v | Write valid huge_zero_pfn Overwrite huge_zero_pfn with ~0UL <--- Invalid overwrite! This results in is_huge_zero_pfn() and is_huge_zero_pmd() incorrectly returning false for a huge zero page which could result in issues like the huge zero folio being incorrectly split. Note that the issue is with huge_zero_pfn not huge_zero_folio, as get_huge_zero_folio() uses cmpxchg() gated on huge_zero_folio being NULL with a retry loop and shrink_huge_zero_folio_scan() uses xchg() to set huge_zero_folio. Fix the issue by introducing a spinlock, huge_zero_lock, to prevent concurrent write of huge_zero_folio, huge_zero_pfn and huge_zero_refcount. There needs to be significant care taken here to ensure correctness: The fast path in get_huge_zero_folio() uses atomic_inc_not_zero(), which is outside of the critical section, and means huge zero allocation is gated on zero huge_zero_refcount. The fast path doesn't use huge_zero_lock, so the critical section is irrelevant to it. So invariants are required - huge_zero_refcount MUST: * Only be set in the huge_zero_lock critical section to ensure serialisation of huge_zero_pfn, huge_zero_folio and ---truncated---

Quoted source text, attributed separately from HOL analysis.