Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.

Linux kernel <6.6.157.1-1 may cause long pauses

published 2 months ago
Summary

Versions of the Linux kernel older than 6.6.157.1-1 can get stuck for minutes while moving memory pages, which can delay background tasks and affect system responsiveness. Updating the kernel to a version that includes the fix removes the delay and restores normal operation.

What to do
  • Update kernel to version 6.6.157.1-1.
Affected software
Ecosystem VendorProductAffected versions
Azure Linux:3 azure kernel <= 6.6.150.1-1
Azure Linux:3 – kernel <= 6.6.152.1-1
< 6.6.157.1-1
Fix: upgrade to 6.6.157.1-1
Original advisory text
CVE-2026-89756 affecting package kernel for versions less than 6.6.157.1-1
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]
Timeline
Published11 Sep 2026
Updated2 Oct 2026
First seen23 Sep 2026
Sources
AZL-100887 · OSV
Track software like this
Free during beta