HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

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.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 74657 ipv4 fix fibnlmsgsize for rtavia nexthops
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
  • 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-74657

ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthopsCVE-2026-74657

Answer in brief

CVE-2026-74657 records a Unknown severity vulnerability in ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthops. 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 22, 2026Updated Aug 27, 2026Source checked Oct 7, 2026First seen by HOL Aug 22, 2026Material review Aug 27, 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>=d15662682db232da77136cd348f4c9df312ca6f9 <0f0ca602941d0a81ae9514943ca06c55159c6385 || >=d15662682db232da77136cd348f4c9df312ca6f9 <5307a53599fa762c06e475ee4a375252074fd324 || >=d15662682db232da77136cd348f4c9df312ca6f9 <7f80ad373ce4a7af5367ff273cea0f16e91387f3 || >=d15662682db232da77136cd348f4c9df312ca6f9 <4a5dfbae5179f6574695012a980476254df2d295 || >=d15662682db232da77136cd348f4c9df312ca6f9 <a59edda6eda1252340354322d8ab318b2e9052fb || >=d15662682db232da77136cd348f4c9df312ca6f9 <9b22f13524fa0de0d963bbd3002df6c28bae3395 || >=d15662682db232da77136cd348f4c9df312ca6f9 <4ff9548d84945d2cbf9e4c207288063a200ea3970f0ca602941d0a81ae9514943ca06c55159c6385, 5307a53599fa762c06e475ee4a375252074fd324, 7f80ad373ce4a7af5367ff273cea0f16e91387f3, 4a5dfbae5179f6574695012a980476254df2d295, a59edda6eda1252340354322d8ab318b2e9052fb, 9b22f13524fa0de0d963bbd3002df6c28bae3395, 4ff9548d84945d2cbf9e4c207288063a200ea397
Linux/Linuxgeneric5.2Not reported
Linux/Linuxgeneric>=d15662682db232da77136cd348f4c9df312ca6f9 <57195f0ab5cfbb5ee0864e5aff15ceb48f5a5e28 || >=d15662682db232da77136cd348f4c9df312ca6f9 <0f0ca602941d0a81ae9514943ca06c55159c6385 || >=d15662682db232da77136cd348f4c9df312ca6f9 <5307a53599fa762c06e475ee4a375252074fd324 || >=d15662682db232da77136cd348f4c9df312ca6f9 <7f80ad373ce4a7af5367ff273cea0f16e91387f3 || >=d15662682db232da77136cd348f4c9df312ca6f9 <4a5dfbae5179f6574695012a980476254df2d295 || >=d15662682db232da77136cd348f4c9df312ca6f9 <a59edda6eda1252340354322d8ab318b2e9052fb || >=d15662682db232da77136cd348f4c9df312ca6f9 <9b22f13524fa0de0d963bbd3002df6c28bae3395 || >=d15662682db232da77136cd348f4c9df312ca6f9 <4ff9548d84945d2cbf9e4c207288063a200ea39757195f0ab5cfbb5ee0864e5aff15ceb48f5a5e28, 0f0ca602941d0a81ae9514943ca06c55159c6385, 5307a53599fa762c06e475ee4a375252074fd324, 7f80ad373ce4a7af5367ff273cea0f16e91387f3, 4a5dfbae5179f6574695012a980476254df2d295, a59edda6eda1252340354322d8ab318b2e9052fb, 9b22f13524fa0de0d963bbd3002df6c28bae3395, 4ff9548d84945d2cbf9e4c207288063a200ea397

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

Evidence timeline and material changes

  1. Published upstream

    Aug 22, 2026

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

    Aug 27, 2026

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

    Aug 22, 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: Fix fib_nlmsg_size() for RTA_VIA nexthops fib_nlmsg_size() still estimates nexthop space as if every gateway is encoded as an IPv4 RTA_GATEWAY attribute. IPv4 routes can also carry an IPv6 gateway, which fib_nexthop_info() dumps as RTA_VIA. As a result, route notifications can allocate an skb that is too small. fib_dump_info() then fails with -EMSGSIZE and rtmsg_fib() hits the WARN_ON() that marks such failures as a fib_nlmsg_size() bug. With panic_on_warn set, this becomes a kernel panic. Mirror the actual nexthop dump layout in fib_nlmsg_size(): account for IPv6 nexthop gateways dumped as RTA_VIA, for the no-header rtnexthop layout used inside RTA_MULTIPATH, and for RTA_FLOW only when it is actually present.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Gitea OAuth2 refresh token grant accepts access tokensSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem

Record context

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