CVE-2026-89753

mm/vmscan: report RCU-tasks quiescent states in shrink_lruvec()

N/A
Published: September 11, 2026 at 07:46 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: mm/vmscan: report RCU-tasks quiescent states in shrink_lruvec() I am seeing some rcu_tasks stalls in the Meta fleet during reclaim. INFO: rcu_tasks detected stalls on tasks: 0000000088620d09: .. nvcsw: 6735/6735 holdout: 1 idle_cpu: -1/8 task:GlobalCPUThread state:R running task pid:2552016 tgid:2524552 Call Trace: shrink_lruvec mem_cgroup_iter shrink_node do_try_to_free_pages try_to_free_pages __alloc_frozen_pages_noprof alloc_pages_noprof pte_alloc_one __pte_alloc handle_mm_fault Nothing promises direct reclaim returns in bounded time, and the scan loop in shrink_lruvec() only calls cond_resched(), which is a no-op on PREEMPTION kernels. Involuntary preemption is not a Tasks-RCU quiescent state, so the reclaiming task never reports one and becomes a holdout. Upgrade it to cond_resched_tasks_rcu_qs(), which reports a quiescent state even when cond_resched() does nothing. PS: This has been discussed in [1]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.188315f42295d2667a7f942f154b73a86fd7cb2227
Vendor states this is fixed in 029c9408049f7f582230322057b7075bea594fd5 (fixed)
Vendor states this is fixed in 25f52e81216884a7444bf07a606691feb09a94e3 (fixed)
Vendor states this is fixed in 3fd50239986302cb050d3649351bcec00fa9d5ab (fixed)
Vendor states this is fixed in 4cdc1bdf40944de5c6b118fef07ad23f07844338 (fixed)
Vendor states this is fixed in 4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57 (fixed)
Vendor states this is fixed in a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b (fixed)
Vendor states this is fixed in b5391676c61d94ffe3272dcf6723738b802f79e8 (fixed)
Vendor states this is fixed in cf3ba0911a1cf8680371ff113b90088edd01d2bb (fixed)
Vendor states this is fixed in 3.18 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card