CVE-2026-89753 — mm/vmscan: report RCU-tasks quiescent states in shrink_lruvec()
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]
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < 4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < 4cdc1bdf40944de5c6b118fef07ad23f07844338≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < 029c9408049f7f582230322057b7075bea594fd5≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < b5391676c61d94ffe3272dcf6723738b802f79e8≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < 3fd50239986302cb050d3649351bcec00fa9d5ab≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < cf3ba0911a1cf8680371ff113b90088edd01d2bb≥ 8315f42295d2667a7f942f154b73a86fd7cb2227 and < 25f52e81216884a7444bf07a606691feb09a94e3 and 1 moreversion 3.18 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 20, 2026 · 5 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/cf3ba0911a1cf8680371ff113b90088edd01d2bb
- github.com/advisories/GHSA-vf4v-9g5v-367g
- git.kernel.org/stable/c/25f52e81216884a7444bf07a606691feb09a94e3
- git.kernel.org/stable/c/4cdc1bdf40944de5c6b118fef07ad23f07844338
- git.kernel.org/stable/c/4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57
- git.kernel.org/stable/c/029c9408049f7f582230322057b7075bea594fd5
- git.kernel.org/stable/c/a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b
- git.kernel.org/stable/c/b5391676c61d94ffe3272dcf6723738b802f79e8
- nvd.nist.gov/vuln/detail/CVE-2026-89753
- git.kernel.org/stable/c/3fd50239986302cb050d3649351bcec00fa9d5ab
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98869 bpf: Infer zext_dst based on static register liveness analysis 1h
- Unknown CVE-2023-7356 Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID 1h
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 3d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 3d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 3d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89753 is "mm/vmscan: report RCU-tasks quiescent states in shrink_lruvec()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.