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 89555 mpls reload header after pskbmaypull
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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Critical · CVSS 9.8CVE-2026-89555

mpls: reload header after pskb_may_pull()CVE-2026-89555

Answer in brief

CVE-2026-89555 records a Critical severity (CVSS 9.8) vulnerability in mpls: reload header after pskb_may_pull(). 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 Sep 11, 2026Updated Oct 19, 2026Source checked Oct 27, 2026First seen by HOL Sep 11, 2026Material review Oct 19, 2026
Upstream Advisory

Record context

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

Key facts

Risk
Critical · CVSS 9.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 9.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>=9f427a0e474a67b454420c131709600d44850486 <fed638a248116b8a249bd4202d28e5934bdc65ad || >=9f427a0e474a67b454420c131709600d44850486 <d82b90a38c2ca8a0694428eab0e9551c23f2447d || >=9f427a0e474a67b454420c131709600d44850486 <49d38c1b4390412f8950d33dfaee0ccbd17beb81 || >=9f427a0e474a67b454420c131709600d44850486 <29e63b8d9fc150cc191b1c6eb7e16e1247e1b650 || ad864d9fce0ec56cc8f6afe5c6a0e6d7f484b9eb || >=4.9.8 <4.10fed638a248116b8a249bd4202d28e5934bdc65ad, d82b90a38c2ca8a0694428eab0e9551c23f2447d, 49d38c1b4390412f8950d33dfaee0ccbd17beb81, 29e63b8d9fc150cc191b1c6eb7e16e1247e1b650, 4.10
Linux/Linuxgeneric4.10Not reported
Linux/Linuxgeneric>=9f427a0e474a67b454420c131709600d44850486 <aa4fe0b450a461aa1162fe8375f5d28f4c957df8 || >=9f427a0e474a67b454420c131709600d44850486 <b1c0783b2facc398437ad8f8b86c636d7a78f8db || >=9f427a0e474a67b454420c131709600d44850486 <bfaaff99238326166694354a63a76c02563f98b1 || >=9f427a0e474a67b454420c131709600d44850486 <d9640239827d6d0cb84263b590f7a4f1596c17eb || >=9f427a0e474a67b454420c131709600d44850486 <fed638a248116b8a249bd4202d28e5934bdc65ad || >=9f427a0e474a67b454420c131709600d44850486 <d82b90a38c2ca8a0694428eab0e9551c23f2447d || >=9f427a0e474a67b454420c131709600d44850486 <49d38c1b4390412f8950d33dfaee0ccbd17beb81 || >=9f427a0e474a67b454420c131709600d44850486 <29e63b8d9fc150cc191b1c6eb7e16e1247e1b650 || ad864d9fce0ec56cc8f6afe5c6a0e6d7f484b9eb || >=4.9.8 <4.10aa4fe0b450a461aa1162fe8375f5d28f4c957df8, b1c0783b2facc398437ad8f8b86c636d7a78f8db, bfaaff99238326166694354a63a76c02563f98b1, d9640239827d6d0cb84263b590f7a4f1596c17eb, fed638a248116b8a249bd4202d28e5934bdc65ad, d82b90a38c2ca8a0694428eab0e9551c23f2447d, 49d38c1b4390412f8950d33dfaee0ccbd17beb81, 29e63b8d9fc150cc191b1c6eb7e16e1247e1b650, 4.10

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

Evidence timeline and material changes

  1. Published upstream

    Sep 11, 2026

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

    Oct 19, 2026

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

    Sep 11, 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: mpls: reload header after pskb_may_pull() mpls_select_multipath() calls mpls_multipath_hash() to choose a nexthop when an MPLS route has multiple nexthops. While walking the MPLS label stack, the hash routine caches hdr for the current label. After finding the bottom-of-stack label, it calls pskb_may_pull() before reading the inner IP header. If an skb is constructed with the inner IP header in nonlinear data and insufficient tailroom in the linear head, pskb_may_pull() calls pskb_expand_head() to replace the skb head and free the old one. This leaves hdr pointing to freed memory. The IPv6 path can invalidate hdr again when it performs a second pull for the larger header. The issue was found through static analysis. A reproducer sending a legal Geneve packet through a bareudp/MPLS multipath setup triggered the same KASAN report in 2 of 2 unpatched runs: BUG: KASAN: slab-use-after-free in mpls_select_multipath Read of size 1 at addr ffff88800ecc6e20 by task ksoftirqd/1/23 Call Trace: mpls_select_multipath mpls_forward __netif_receive_skb_list_core netif_receive_skb_list_internal napi_complete_done gro_cell_poll __napi_poll net_rx_action Freed by task 23: kfree pskb_expand_head __pskb_pull_tail mpls_select_multipath Reload hdr from the current skb head after each successful pull before deriving the inner IPv4 or IPv6 header pointer.

Quoted source text, attributed separately from HOL analysis.