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 90111 ip6mr do not clone dst in ip6mrcachereport
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
High · CVSS 7.8CVE-2026-90111

ip6mr: do not clone dst in ip6mr_cache_report()CVE-2026-90111

Answer in brief

CVE-2026-90111 records a High severity (CVSS 7.8) vulnerability in ip6mr: do not clone dst in ip6mr_cache_report(). 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) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

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

Published Sep 17, 2026Updated Oct 30, 2026Source checked Nov 2, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

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

Key facts

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

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=67f415dd29063a5906c560051c00e42dcf01a4dd <4a674afaae4136c71943aa3e35d433676fd40e8f || >=67f415dd29063a5906c560051c00e42dcf01a4dd <235b42b5860189eb8c27c36435ad932cae65a7344a674afaae4136c71943aa3e35d433676fd40e8f, 235b42b5860189eb8c27c36435ad932cae65a734
Linux/Linuxgeneric5.3Not reported
Linux/Linuxgeneric>=67f415dd29063a5906c560051c00e42dcf01a4dd <f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89 || >=67f415dd29063a5906c560051c00e42dcf01a4dd <4a674afaae4136c71943aa3e35d433676fd40e8f || >=67f415dd29063a5906c560051c00e42dcf01a4dd <235b42b5860189eb8c27c36435ad932cae65a734f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89, 4a674afaae4136c71943aa3e35d433676fd40e8f, 235b42b5860189eb8c27c36435ad932cae65a734
Linux/Linuxgeneric>=67f415dd29063a5906c560051c00e42dcf01a4dd <7f8287f606c8c028d4224e85d95dc448c6d6d623 || >=67f415dd29063a5906c560051c00e42dcf01a4dd <42ef371466d5648f5c9e8bc219f0af0a2c2bbf8c || >=67f415dd29063a5906c560051c00e42dcf01a4dd <f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89 || >=67f415dd29063a5906c560051c00e42dcf01a4dd <4a674afaae4136c71943aa3e35d433676fd40e8f || >=67f415dd29063a5906c560051c00e42dcf01a4dd <235b42b5860189eb8c27c36435ad932cae65a7347f8287f606c8c028d4224e85d95dc448c6d6d623, 42ef371466d5648f5c9e8bc219f0af0a2c2bbf8c, f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89, 4a674afaae4136c71943aa3e35d433676fd40e8f, 235b42b5860189eb8c27c36435ad932cae65a734
Linux/Linuxgeneric>=67f415dd29063a5906c560051c00e42dcf01a4dd <b50d3cfb8513e895cee453dd0f834deee6ccc231 || >=67f415dd29063a5906c560051c00e42dcf01a4dd <7f8287f606c8c028d4224e85d95dc448c6d6d623 || >=67f415dd29063a5906c560051c00e42dcf01a4dd <42ef371466d5648f5c9e8bc219f0af0a2c2bbf8c || >=67f415dd29063a5906c560051c00e42dcf01a4dd <f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89 || >=67f415dd29063a5906c560051c00e42dcf01a4dd <4a674afaae4136c71943aa3e35d433676fd40e8f || >=67f415dd29063a5906c560051c00e42dcf01a4dd <235b42b5860189eb8c27c36435ad932cae65a734b50d3cfb8513e895cee453dd0f834deee6ccc231, 7f8287f606c8c028d4224e85d95dc448c6d6d623, 42ef371466d5648f5c9e8bc219f0af0a2c2bbf8c, f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89, 4a674afaae4136c71943aa3e35d433676fd40e8f, 235b42b5860189eb8c27c36435ad932cae65a734

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 4a674afaae4136c71943aa3e35d433676fd40e8f; Linux/Linux to f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89; Linux/Linux to 7f8287f606c8c028d4224e85d95dc448c6d6d623; Linux/Linux to b50d3cfb8513e895cee453dd0f834deee6ccc231 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 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

    Sep 17, 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: ip6mr: do not clone dst in ip6mr_cache_report() IPv6 input attaches a non-refcounted (NOREF) dst to skbs under RCU. When an ingress multicast packet misses MFC lookup, ip6mr_cache_unresolved() places the skb onto the unresolved queue, escaping the receive-side RCU grace period. If the underlying route is deleted and freed, and the MFC queue is later resolved with a wrong parent interface, ip6_mr_forward() invokes ip6mr_cache_report(..., MRT6MSG_WRONGMIF), which executes dst_clone(skb_dst(pkt)) on the freed dst entry, triggering a slab use-after-free. Report packets queued to mroute6_sk (a raw socket) and netlink notifications do not require an attached dst entry. Fix this by: 1. Removing dst_clone() in ip6mr_cache_report() and ensuring report skbs do not hold a dst. 2. Dropping skb_dst before queuing unresolved skbs in ip6mr_cache_unresolved(), matching the fact that multicast forwarding resolves outgoing routes anew via ip6_route_output().

Quoted source text, attributed separately from HOL analysis.