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 64579 xfrm policy preallocate inexact bins before
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
Unknown severity · Source severity not reportedCVE-2026-64579

xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsertCVE-2026-64579

Answer in brief

CVE-2026-64579 records a Unknown severity vulnerability in xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert. The current sources do not mark it as known exploited. The current feed maps 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 5, 2026Updated Aug 19, 2026Source checked Nov 4, 2026First seen by HOL Aug 5, 2026Material review Aug 19, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=24969facd704a5f0dd8e08da86bf32a9ce972bee <d9d9cc21cc90014724a14c447e3d587be9447107 || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <94c00391a5117530188334f740ce26d3f1256190 || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <7acc5ed2f33608a3d83b64f50a5766843b6e2485 || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <6aa3796d18a9fda953ad76a62b57bf6c145cb9ef || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <f38f8cce2f7e79775b3db7e8a5eacda04ac908e4d9d9cc21cc90014724a14c447e3d587be9447107, 94c00391a5117530188334f740ce26d3f1256190, 7acc5ed2f33608a3d83b64f50a5766843b6e2485, 6aa3796d18a9fda953ad76a62b57bf6c145cb9ef, f38f8cce2f7e79775b3db7e8a5eacda04ac908e4
Linux/Linuxgeneric5.0Not reported
Linux/Linuxgeneric>=24969facd704a5f0dd8e08da86bf32a9ce972bee <e48f4c3e3df35b34be719d72d737bbeaca77cf0c || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <1cdeed9df1306f1a277e715600772640d63defa9 || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <43a4d510523779891cf8eca7ffb4a086b0b5d8bf || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <d9d9cc21cc90014724a14c447e3d587be9447107 || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <94c00391a5117530188334f740ce26d3f1256190 || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <7acc5ed2f33608a3d83b64f50a5766843b6e2485 || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <6aa3796d18a9fda953ad76a62b57bf6c145cb9ef || >=24969facd704a5f0dd8e08da86bf32a9ce972bee <f38f8cce2f7e79775b3db7e8a5eacda04ac908e4e48f4c3e3df35b34be719d72d737bbeaca77cf0c, 1cdeed9df1306f1a277e715600772640d63defa9, 43a4d510523779891cf8eca7ffb4a086b0b5d8bf, d9d9cc21cc90014724a14c447e3d587be9447107, 94c00391a5117530188334f740ce26d3f1256190, 7acc5ed2f33608a3d83b64f50a5766843b6e2485, 6aa3796d18a9fda953ad76a62b57bf6c145cb9ef, f38f8cce2f7e79775b3db7e8a5eacda04ac908e4

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

Evidence timeline and material changes

  1. Published upstream

    Aug 5, 2026

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

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

In the Linux kernel, the following vulnerability has been resolved: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert xfrm_hash_rebuild()'s first loop preallocates the bins/chains the reinsert loop needs, so the reinsert (after hlist_del_rcu()) cannot allocate or fail. But its guard is inverted: it skips policies with prefixlen < threshold and preallocates for the rest. prefixlen < threshold is exactly when policy_hash_bysel() returns NULL and the reinsert takes the allocating xfrm_policy_inexact_insert() path. So the loop preallocates for the exact policies (which never allocate) and skips the inexact ones, whose bin/node is then allocated GFP_ATOMIC during reinsert. On failure the error path only WARN_ONCE()s and continues, leaving a poisoned bydst node; the next rebuild's hlist_del_rcu() dereferences LIST_POISON2 and takes a GPF. Reachable under memory pressure, deterministic via failslab. Invert the guard so preallocation covers exactly the reinserted policies; the reinsert then allocates nothing and cannot fail. Crash: Oops: general protection fault, probably for non-canonical address 0xfbd59c0000000024: 0000 [#1] SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0xdead...] ... Workqueue: events xfrm_hash_rebuild RIP: 0010:xfrm_hash_rebuild+0x5b3/0x1190 RAX: dead000000000122 (LIST_POISON2 + offset) ... Call Trace: hlist_del_rcu (include/linux/rculist.h:599) xfrm_hash_rebuild (net/xfrm/xfrm_policy.c:1365) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) ... Kernel panic - not syncing: Fatal exception in interrupt

Quoted source text, attributed separately from HOL analysis.

Record context

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