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 89796 mmdamoncore avoid infinite kdamondmergeregions
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
Unknown severity · Source severity not reportedCVE-2026-89796

mm/damon/core: avoid infinite kdamond_merge_regions() internal loopCVE-2026-89796

Answer in brief

CVE-2026-89796 records a Unknown severity vulnerability in mm/damon/core: avoid infinite kdamond_merge_regions() internal loop. 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). 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 16, 2026Updated Oct 19, 2026Source checked Oct 31, 2026First seen by HOL Sep 16, 2026Material review Oct 19, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
4 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=1e865019cef354a5f0314491b4b4fc9f9a613642 <407da1dd7f48e5ba22ceb8834f6923390632d025 || >=d7eda72e59bbf3ed592db7ff0fd8c246c73149a8 <65edd8b3a88278c9f8e5c7d8c15d4f296ce35078 || >=11078e2d11465518a9e85096bd28f8cd5fa1ea41 <5b0953f86d65855dc901050f40bbe6da0475d198 || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <769c16699c89811386eb003c8fd9dcb8d405b316 || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <50a7a5aec1aa43efc297fd4377c1cbdc7d15620d || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <8a96a06e04d210845be5d9581c0e9e338947e8f8 || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <123e4619ab6c8ab1c4cb1d7a58311a2af13929cd || f2bd3184b6aeca6a497394b558337246e09fc02d || >=5.15.164 <5.15.222 || >=6.1.101 <6.1.189 || >=6.6.41 <6.6.158 || >=6.9.10 <6.10407da1dd7f48e5ba22ceb8834f6923390632d025, 65edd8b3a88278c9f8e5c7d8c15d4f296ce35078, 5b0953f86d65855dc901050f40bbe6da0475d198, 769c16699c89811386eb003c8fd9dcb8d405b316, 50a7a5aec1aa43efc297fd4377c1cbdc7d15620d, 8a96a06e04d210845be5d9581c0e9e338947e8f8, 123e4619ab6c8ab1c4cb1d7a58311a2af13929cd, 5.15.222, 6.1.189, 6.6.158, 6.10
Linux/Linuxgeneric6.10Not reported
Linux/Linuxgeneric>=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <8a96a06e04d210845be5d9581c0e9e338947e8f8 || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <123e4619ab6c8ab1c4cb1d7a58311a2af13929cd || 1e865019cef354a5f0314491b4b4fc9f9a613642 || d7eda72e59bbf3ed592db7ff0fd8c246c73149a8 || 11078e2d11465518a9e85096bd28f8cd5fa1ea41 || f2bd3184b6aeca6a497394b558337246e09fc02d || >=5.15.164 <5.16 || >=6.1.101 <6.2 || >=6.6.41 <6.7 || >=6.9.10 <6.108a96a06e04d210845be5d9581c0e9e338947e8f8, 123e4619ab6c8ab1c4cb1d7a58311a2af13929cd, 5.16, 6.2, 6.7, 6.10
Linux/Linuxgeneric>=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <769c16699c89811386eb003c8fd9dcb8d405b316 || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <50a7a5aec1aa43efc297fd4377c1cbdc7d15620d || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <8a96a06e04d210845be5d9581c0e9e338947e8f8 || >=310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 <123e4619ab6c8ab1c4cb1d7a58311a2af13929cd || 1e865019cef354a5f0314491b4b4fc9f9a613642 || d7eda72e59bbf3ed592db7ff0fd8c246c73149a8 || 11078e2d11465518a9e85096bd28f8cd5fa1ea41 || f2bd3184b6aeca6a497394b558337246e09fc02d || >=5.15.164 <5.16 || >=6.1.101 <6.2 || >=6.6.41 <6.7 || >=6.9.10 <6.10769c16699c89811386eb003c8fd9dcb8d405b316, 50a7a5aec1aa43efc297fd4377c1cbdc7d15620d, 8a96a06e04d210845be5d9581c0e9e338947e8f8, 123e4619ab6c8ab1c4cb1d7a58311a2af13929cd, 5.16, 6.2, 6.7, 6.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 407da1dd7f48e5ba22ceb8834f6923390632d025; Linux/Linux to 8a96a06e04d210845be5d9581c0e9e338947e8f8; Linux/Linux to 769c16699c89811386eb003c8fd9dcb8d405b316 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 16, 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 16, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: avoid infinite kdamond_merge_regions() internal loop Patch series "mm/damon: unurgent fixes for infinite loop, NULL de-ref and races", v1.1. Sashiko found a few issues in DAMON that could cause infinite loop, NULL dereference and monitoring results degradation. The first two sounds scary but the infinite loop happens only under unreasonable user setup. The NULL dereference is only in a unit test. Monitoring results degradation is trivial since it is only best-effort, and those happens from only unlikely races. Still those are bugs that better to fix if possible. Fix those. This patch (of 6): Due to online parameter update like events, the number of DAMON regions could be higher than the user-set upper limit. kdamond_merge_regions() repeats merge regions until the number meets the limit, while doubling the merge threshold up to the theoretical maximum threshold. It is tried only up to the theoretical maximum threshold because even the aggressive merging can fail from reducing the number of regions under the user-defined upper limit. For example, there could be many user-defined non-contiguous regions that cannot be merged. The threshold based loop break condition is evaluated by comparing the threshold for the next merging try against the theoretical maximum threshold. If max_thres is larger than UINT_MAX / 2, doubling the threshold could make it overflow, and bypass the loop break condition. In the case, if the number of regions cannot be reduced under the upper limit like explained above, the loop will run infinitely. Prevent the case by doing the break condition check before doubling the threshold. Also, prevent the threshold exceeding the maximum threshold, as it could overflow and apply the wrong merge threshold. This issue is unlikely to occur in real world, since having the max_thres higher than UINT_MAX / 2 require unrealistically large aggregation intervals compared to the sampling interval. Also, it requires an unrealistically large number of uncontiguous regions setup. Nonetheless, the consequence is bad and the fix is simple. The issue was discovered [1] by Sashiko.

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