mm/vmscan: report RCU-tasks quiescent states in shrink_lruvec()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 029c9408049f7f582230322057b7075bea594fd5, 25f52e81216884a7444bf07a606691feb09a94e3, 3fd50239986302cb050d3649351bcec00fa9d5ab; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 029c9408049f7f582230322057b7075bea594fd5, 25f52e81216884a7444bf07a606691feb09a94e3, 3fd50239986302cb050d3649351bcec00fa9d5ab; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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]
- Published
- Sep 11, 2026
- Updated
- Sep 14, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.18affected
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before 4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57affected · git
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before 4cdc1bdf40944de5c6b118fef07ad23f07844338affected · git
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before a67a00a70a7c8309ca47ea157ef3e8ed3d268f5baffected · git
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before 029c9408049f7f582230322057b7075bea594fd5affected · git
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before b5391676c61d94ffe3272dcf6723738b802f79e8affected · git
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before 3fd50239986302cb050d3649351bcec00fa9d5abaffected · git
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before cf3ba0911a1cf8680371ff113b90088edd01d2bbaffected · git
- 8315f42295d2667a7f942f154b73a86fd7cb2227 and later · before 25f52e81216884a7444bf07a606691feb09a94e3affected · git
- before 3.18not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-72421ipv4: fib: Don't ignore error route in local/main tables.40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 029c9408049f7f582230322057b7075bea594fd5 | Vendor (CNA) |
| Linux Linux | 25f52e81216884a7444bf07a606691feb09a94e3 | Vendor (CNA) |
| Linux Linux | 3fd50239986302cb050d3649351bcec00fa9d5ab | Vendor (CNA) |
| Linux Linux | 4cdc1bdf40944de5c6b118fef07ad23f07844338 | Vendor (CNA) |
| Linux Linux | 4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57 | Vendor (CNA) |
| Linux Linux | a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b | Vendor (CNA) |
| Linux Linux | b5391676c61d94ffe3272dcf6723738b802f79e8 | Vendor (CNA) |
| Linux Linux | cf3ba0911a1cf8680371ff113b90088edd01d2bb | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/25f52e81216884a7444bf07a606691feb09a94e3
- git.kernel.org/stable/c/3fd50239986302cb050d3649351bcec00fa9d5ab
- git.kernel.org/stable/c/4cdc1bdf40944de5c6b118fef07ad23f07844338
- git.kernel.org/stable/c/4f50593c9cbc883d8c9b50148a3e8a8b1fd35f57
- git.kernel.org/stable/c/a67a00a70a7c8309ca47ea157ef3e8ed3d268f5b
- git.kernel.org/stable/c/b5391676c61d94ffe3272dcf6723738b802f79e8
- git.kernel.org/stable/c/cf3ba0911a1cf8680371ff113b90088edd01d2bb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.