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 64543 tipc fix use after free of the discoverer in
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-64543

tipc: fix use-after-free of the discoverer in tipc_disc_rcv()CVE-2026-64543

Answer in brief

CVE-2026-64543 records a High severity (CVSS 7.8) vulnerability in tipc: fix use-after-free of the discoverer in tipc_disc_rcv(). 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 Jul 27, 2026Updated Nov 3, 2026Source checked Nov 4, 2026First seen by HOL Aug 5, 2026Material review Nov 3, 2026
Upstream Advisory

Key facts

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

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <5e215bf1c47fdddf8203a0fe80a0ed594065f101 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <ec7d54d8cc1723921d671e3272b427c96366506f || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <a0c5fdeb5fa257f8c6d469af266bc087cb5de6a2 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <b65289e1c3f352a9f92c6e19713ddd647e033253 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <1579342d71133da7f00daa02c75cebec7372097b5e215bf1c47fdddf8203a0fe80a0ed594065f101, ec7d54d8cc1723921d671e3272b427c96366506f, a0c5fdeb5fa257f8c6d469af266bc087cb5de6a2, b65289e1c3f352a9f92c6e19713ddd647e033253, 1579342d71133da7f00daa02c75cebec7372097b
Linux/Linuxgeneric4.17Not reported
Linux/Linuxgeneric>=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <380413cdfd29fb9fa486c82889132b680c4983c5 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <f05b3f4c78370469286879c765f5a1dd39dbcd32 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <4da2ac7749411971e1b222b992da5a172ce45f98 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <5e215bf1c47fdddf8203a0fe80a0ed594065f101 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <ec7d54d8cc1723921d671e3272b427c96366506f || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <a0c5fdeb5fa257f8c6d469af266bc087cb5de6a2 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <b65289e1c3f352a9f92c6e19713ddd647e033253 || >=25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 <1579342d71133da7f00daa02c75cebec7372097b380413cdfd29fb9fa486c82889132b680c4983c5, f05b3f4c78370469286879c765f5a1dd39dbcd32, 4da2ac7749411971e1b222b992da5a172ce45f98, 5e215bf1c47fdddf8203a0fe80a0ed594065f101, ec7d54d8cc1723921d671e3272b427c96366506f, a0c5fdeb5fa257f8c6d469af266bc087cb5de6a2, b65289e1c3f352a9f92c6e19713ddd647e033253, 1579342d71133da7f00daa02c75cebec7372097b

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

Evidence timeline and material changes

  1. Published upstream

    Jul 27, 2026

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

    Nov 3, 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: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() bearer_disable() frees b->disc with tipc_disc_delete()'s plain kfree(), but tipc_disc_rcv() still dereferences b->disc in RX softirq under rcu_read_lock() (tipc_udp_recv -> tipc_rcv -> tipc_disc_rcv). L2 bearers are safe thanks to the synchronize_net() in tipc_disable_l2_media(), but the UDP bearer defers that call to the cleanup_bearer() workqueue, so the discoverer is freed with no grace period: BUG: KASAN: slab-use-after-free in tipc_disc_rcv (net/tipc/discover.c:149) Read of size 8 at addr ffff88802348b728 by task poc_tipc/184 <IRQ> tipc_disc_rcv (net/tipc/discover.c:149) tipc_rcv (net/tipc/node.c:2126) tipc_udp_recv (net/tipc/udp_media.c:391) udp_rcv (net/ipv4/udp.c:2643) ip_local_deliver_finish (net/ipv4/ip_input.c:241) </IRQ> Freed by task 181: kfree (mm/slub.c:6565) bearer_disable (net/tipc/bearer.c:418) tipc_nl_bearer_disable (net/tipc/bearer.c:1001) The bearer is freed with kfree_rcu(); free the discoverer the same way. Add an rcu_head to struct tipc_discoverer and free it and its skb from an RCU callback. Because the RCU callback (tipc_disc_free_rcu) lives in module text, a call_rcu() that is still pending when the tipc module is unloaded would invoke a freed function. Add an rcu_barrier() to tipc_exit() after the bearer subsystem has been torn down, so all pending discoverer callbacks have run before the module text goes away. Reachable from an unprivileged user namespace: the TIPCv2 genl family is netnsok and its bearer commands have no GENL_ADMIN_PERM. Needs CONFIG_TIPC and CONFIG_TIPC_MEDIA_UDP.

Quoted source text, attributed separately from HOL analysis.

Record context

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