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 89756 mmmigrate report rcu tasks quiescent states 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
  • 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-89756

mm/migrate: report RCU-tasks quiescent states in migrate_pages_batch()CVE-2026-89756

Answer in brief

CVE-2026-89756 records a Unknown severity vulnerability in mm/migrate: report RCU-tasks quiescent states in migrate_pages_batch(). 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 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
6 linked sources
Open source record

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>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4996a7bc01ef35570664854dac2530c604981039 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5dc0daff0341c6baba19c38f47d299ac831d7e99 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <66734981b4d3c105223a13c827c9c73be18d91ad || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <efe8f86c0916f0f74eea74ae21a3b37f728c6bad || >=0 <6.12.109 || >=0 <6.18.50 || >=0 <7.2.44996a7bc01ef35570664854dac2530c604981039, 5dc0daff0341c6baba19c38f47d299ac831d7e99, 66734981b4d3c105223a13c827c9c73be18d91ad, efe8f86c0916f0f74eea74ae21a3b37f728c6bad, 6.12.109, 6.18.50, 7.2.4
Linux/Linuxgeneric>=8315f42295d2667a7f942f154b73a86fd7cb2227 <4996a7bc01ef35570664854dac2530c604981039 || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <5dc0daff0341c6baba19c38f47d299ac831d7e99 || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <66734981b4d3c105223a13c827c9c73be18d91ad || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <efe8f86c0916f0f74eea74ae21a3b37f728c6bad4996a7bc01ef35570664854dac2530c604981039, 5dc0daff0341c6baba19c38f47d299ac831d7e99, 66734981b4d3c105223a13c827c9c73be18d91ad, efe8f86c0916f0f74eea74ae21a3b37f728c6bad
Linux/Linuxgeneric3.18Not reported
Linux/Linuxgeneric>=8315f42295d2667a7f942f154b73a86fd7cb2227 <8c6d63d434ebb85c6cf3dac1e70a171b183c6614 || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <4757542649af56d894e25e30f57cd497dffad53f || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <4996a7bc01ef35570664854dac2530c604981039 || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <5dc0daff0341c6baba19c38f47d299ac831d7e99 || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <66734981b4d3c105223a13c827c9c73be18d91ad || >=8315f42295d2667a7f942f154b73a86fd7cb2227 <efe8f86c0916f0f74eea74ae21a3b37f728c6bad8c6d63d434ebb85c6cf3dac1e70a171b183c6614, 4757542649af56d894e25e30f57cd497dffad53f, 4996a7bc01ef35570664854dac2530c604981039, 5dc0daff0341c6baba19c38f47d299ac831d7e99, 66734981b4d3c105223a13c827c9c73be18d91ad, efe8f86c0916f0f74eea74ae21a3b37f728c6bad

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 4996a7bc01ef35570664854dac2530c604981039; Linux/Linux to 4996a7bc01ef35570664854dac2530c604981039; Linux/Linux to 8c6d63d434ebb85c6cf3dac1e70a171b183c6614 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: mm/migrate: report RCU-tasks quiescent states in migrate_pages_batch() migrate_pages_batch() unmaps each folio before moving it, and every unmap runs the mmu_notifier invalidate callbacks. On KVM hosts try_to_migrate() ends up in kvm_mmu_notifier_invalidate_range_start() -> tdp_mmu_zap_leafs(), which is expensive, so unmapping a large batch keeps the CPU busy for a long time. The loop already calls cond_resched(), but on PREEMPTION kernels that is a no-op, and involuntary preemption is not a Tasks-RCU quiescent state. A long batch therefore never reports a quiescent state, and the migrating task (e.g. kcompactd) becomes a Tasks-RCU holdout, stalling the Tasks-RCU grace period for minutes, which is common at Meta fleet: INFO: rcu_tasks detected stalls on tasks: 0000000055349ecc: .. nvcsw: 1157401/1157401 holdout: 1 idle_cpu: -1/56 task:kcompactd0 state:R running task Call Trace: tdp_mmu_zap_leafs tdp_mmu_next_root gfn_to_pfn_cache_invalidate_start kvm_mmu_notifier_invalidate_range_start __mmu_notifier_invalidate_range_start try_to_migrate_one try_to_migrate migrate_pages_batch migrate_pages compact_zone compact_node kcompactd kthread Use cond_resched_tasks_rcu_qs() so a quiescent state is reported even when cond_resched() does nothing. This has also been discussed at [1]

Quoted source text, attributed separately from HOL analysis.