CVE-2026-89753

published 11 Sep 2026 · updated 19 Oct 2026

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

4.7MediumCVSS 4.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 029c9408049f7f582230322057b7075bea594fd5, Kernel 25f52e81216884a7444bf07a606691feb09a94e3, Kernel 3fd50239986302cb050d3649351bcec00fa9d5ab and 5 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.18, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <029c9408049f7f582230322057b7075bea594fd5, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <25f52e81216884a7444bf07a606691feb09a94e3, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <3fd50239986302cb050d3649351bcec00fa9d5ab, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <4cdc1bdf40944de5c6b118fef07ad23f07844338, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <b5391676c61d94ffe3272dcf6723738b802f79e8, >=8315f42295d2667a7f942f154b73a86fd7cb2227 <cf3ba0911a1cf8680371ff113b90088edd01d2bb029c9408049f7f582230322057b7075bea594fd5, 25f52e81216884a7444bf07a606691feb09a94e3, 3fd50239986302cb050d3649351bcec00fa9d5ab, 4cdc1bdf40944de5c6b118fef07ad23f07844338, 4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57, a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b, b5391676c61d94ffe3272dcf6723738b802f79e8, cf3ba0911a1cf8680371ff113b90088edd01d2bb

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89753 severity on Zeptric[![CVE-2026-89753](https://zeptric.io/badge/cve/CVE-2026-89753.svg)](https://zeptric.io/cve/CVE-2026-89753)