- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]
Timeline
ID reserved
By Linux
Published
- 38 days later
· 38 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < 4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < 4cdc1bdf40944de5c6b118fef07ad23f07844338
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < 029c9408049f7f582230322057b7075bea594fd5
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < b5391676c61d94ffe3272dcf6723738b802f79e8
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < 3fd50239986302cb050d3649351bcec00fa9d5ab
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < cf3ba0911a1cf8680371ff113b90088edd01d2bb
- affected 8315f42295d2667a7f942f154b73a86fd7cb2227 – < 25f52e81216884a7444bf07a606691feb09a94e3
- affected 3.18
- unaffected < 3.18
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.109 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57 (opens in a new tab)
- https://git.kernel.org/stable/c/4cdc1bdf40944de5c6b118fef07ad23f07844338 (opens in a new tab)
- https://git.kernel.org/stable/c/a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b (opens in a new tab)
- https://git.kernel.org/stable/c/029c9408049f7f582230322057b7075bea594fd5 (opens in a new tab)
- https://git.kernel.org/stable/c/b5391676c61d94ffe3272dcf6723738b802f79e8 (opens in a new tab)
- https://git.kernel.org/stable/c/3fd50239986302cb050d3649351bcec00fa9d5ab (opens in a new tab)
- https://git.kernel.org/stable/c/cf3ba0911a1cf8680371ff113b90088edd01d2bb (opens in a new tab)
- https://git.kernel.org/stable/c/25f52e81216884a7444bf07a606691feb09a94e3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76665 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89753)Record last updated .