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 64572 ipv4 fib free fibalias with kfreercu on insert
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
Unknown severity ยท Source severity not reportedCVE-2026-64572

ipv4: fib: free fib_alias with kfree_rcu() on insert error pathCVE-2026-64572

Answer in brief

CVE-2026-64572 records a Unknown severity vulnerability in ipv4: fib: free fib_alias with kfree_rcu() on insert error path. 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 3, 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>=a6c76c17df021b141b0d306828c9fe4ba2d2717c <8150b5365f026e72250cacc527ea00be30f40105 || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <d007056868723de9c0cc3f5ffaad47a8d468b9a4 || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <cb8be318b4432abd88d3172ec157330f27a5f7a7 || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <b8d2ea75c76abcd0d72679c2f488271f573e32fb || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <f2f152e94a67bc746afaf05a1b2702c1955531128150b5365f026e72250cacc527ea00be30f40105, d007056868723de9c0cc3f5ffaad47a8d468b9a4, cb8be318b4432abd88d3172ec157330f27a5f7a7, b8d2ea75c76abcd0d72679c2f488271f573e32fb, f2f152e94a67bc746afaf05a1b2702c195553112
Linux/Linuxgeneric5.6Not reported
Linux/Linuxgeneric>=a6c76c17df021b141b0d306828c9fe4ba2d2717c <9d0778571def598c31e84a38ae5a7ebc6f65e6d8 || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <bb03350f974aec352b660d032a1d283eb462165a || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <6429c9cfd941e62acd7bb0bc64d631574d4c3b2a || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <8150b5365f026e72250cacc527ea00be30f40105 || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <d007056868723de9c0cc3f5ffaad47a8d468b9a4 || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <cb8be318b4432abd88d3172ec157330f27a5f7a7 || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <b8d2ea75c76abcd0d72679c2f488271f573e32fb || >=a6c76c17df021b141b0d306828c9fe4ba2d2717c <f2f152e94a67bc746afaf05a1b2702c1955531129d0778571def598c31e84a38ae5a7ebc6f65e6d8, bb03350f974aec352b660d032a1d283eb462165a, 6429c9cfd941e62acd7bb0bc64d631574d4c3b2a, 8150b5365f026e72250cacc527ea00be30f40105, d007056868723de9c0cc3f5ffaad47a8d468b9a4, cb8be318b4432abd88d3172ec157330f27a5f7a7, b8d2ea75c76abcd0d72679c2f488271f573e32fb, f2f152e94a67bc746afaf05a1b2702c195553112

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 8150b5365f026e72250cacc527ea00be30f40105; Linux/Linux to 9d0778571def598c31e84a38ae5a7ebc6f65e6d8 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: ipv4: fib: free fib_alias with kfree_rcu() on insert error path fib_table_insert() publishes new_fa into the leaf's fa_list with fib_insert_alias() before calling the fib entry notifiers. When a notifier fails, the error path removes new_fa with fib_remove_alias() (hlist_del_rcu) and frees it right away with kmem_cache_free(). fib_table_lookup() walks that list under rcu_read_lock() only, so a concurrent lookup that already reached new_fa keeps reading it after the free: BUG: KASAN: slab-use-after-free in fib_table_lookup (net/ipv4/fib_trie.c:1601) Read of size 1 at addr ffff88810676d4eb by task exploit/297 Call Trace: fib_table_lookup (net/ipv4/fib_trie.c:1601) ip_route_output_key_hash_rcu (net/ipv4/route.c:2814) ip_route_output_key_hash (net/ipv4/route.c:2705) __ip4_datagram_connect (net/ipv4/datagram.c:49) udp_connect (net/ipv4/udp.c:2144) __sys_connect (net/socket.c:2167) __x64_sys_connect (net/socket.c:2173) do_syscall_64 entry_SYSCALL_64_after_hwframe which belongs to the cache ip_fib_alias of size 56 Triggering the error path needs CAP_NET_ADMIN and a registered fib notifier that can reject a route; a netdevsim device whose IPv4 FIB resource is exhausted is enough. Free new_fa with alias_free_mem_rcu(), as fib_table_delete() already does for a fib_alias removed from the trie.

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 3, 2026
References
8 linked sources
Open source record