CVE-2026-89753

CVE CVE-2026-89753EUVD EUVD-2026-76665Published 2026-09-11T19:46:56.000ZLast changed 2026-09-14T12:02:33.000Z

What the advisory describes

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]

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 5.15.221; patch: 6.12.109; 8315f42295d2667a7f942f154b73a86fd7cb2227 <a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b; patch: 6.6.157; 8315f42295d2667a7f942f154b73a86fd7cb2227 <25f52e81216884a7444bf07a606691feb09a94e3; 8315f42295d2667a7f942f154b73a86fd7cb2227 <3fd50239986302cb050d3649351bcec00fa9d5ab; patch: 5.10.270; patch: 7.3-rc1; 3.18; patch: 0; 8315f42295d2667a7f942f154b73a86fd7cb2227 <029c9408049f7f582230322057b7075bea594fd5; patch: 6.18.50; 8315f42295d2667a7f942f154b73a86fd7cb2227 <b5391676c61d94ffe3272dcf6723738b802f79e8; 8315f42295d2667a7f942f154b73a86fd7cb2227 <4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57; 8315f42295d2667a7f942f154b73a86fd7cb2227 <cf3ba0911a1cf8680371ff113b90088edd01d2bb; patch: 7.2.4; patch: 6.1.188; 8315f42295d2667a7f942f154b73a86fd7cb2227 <4cdc1bdf40944de5c6b118fef07ad23f07844338

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.