GHSA-VF4V-9G5V-367G
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-14 15:32In 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": [],
"aliases": [
"CVE-2026-89753"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:20:06Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmscan: report RCU-tasks quiescent states in shrink_lruvec()\n\nI am seeing some rcu_tasks stalls in the Meta fleet during reclaim.\n\n INFO: rcu_tasks detected stalls on tasks:\n\t0000000088620d09: .. nvcsw: 6735/6735 holdout: 1 idle_cpu: -1/8\n\ttask:GlobalCPUThread state:R running task pid:2552016 tgid:2524552\n Call Trace:\n shrink_lruvec\n mem_cgroup_iter\n shrink_node\n do_try_to_free_pages\n try_to_free_pages\n __alloc_frozen_pages_noprof\n alloc_pages_noprof\n pte_alloc_one\n __pte_alloc\n handle_mm_fault\n\nNothing promises direct reclaim returns in bounded time, and the scan loop\nin shrink_lruvec() only calls cond_resched(), which is a no-op on\nPREEMPTION kernels. Involuntary preemption is not a Tasks-RCU quiescent\nstate, so the reclaiming task never reports one and becomes a holdout.\n\nUpgrade it to cond_resched_tasks_rcu_qs(), which reports a quiescent state\neven when cond_resched() does nothing.\n\nPS: This has been discussed in [1]",
"id": "GHSA-vf4v-9g5v-367g",
"modified": "2026-09-14T15:32:36Z",
"published": "2026-09-11T21:31:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89753"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/029c9408049f7f582230322057b7075bea594fd5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/25f52e81216884a7444bf07a606691feb09a94e3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3fd50239986302cb050d3649351bcec00fa9d5ab"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4cdc1bdf40944de5c6b118fef07ad23f07844338"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b5391676c61d94ffe3272dcf6723738b802f79e8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cf3ba0911a1cf8680371ff113b90088edd01d2bb"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.