CVE-2026-89753
Description
A flaw was found in the Linux kernel's memory management subsystem. The shrink_lruvec() function, responsible for memory reclaim, fails to properly report Read-Copy-Update (RCU) task quiescent states on systems with preemption enabled. This can lead to RCU task stalls, causing system unresponsiveness or a denial of service.
Statement
A low impact flaw was found in the Linux kernel's memory management subsystem. In the shrink_lruvec() memory reclaim path, the scan loop only calls cond_resched(), which is a no-op on kernels built with PREEMPTION support, and involuntary preemption does not count as a Tasks RCU quiescent state. A task performing direct reclaim under memory pressure can therefore never report a Tasks-RCU quiescent state and becomes a holdout task, triggering rcu_tasks stall warnings that can leave the system unresponsive and result in a local denial of service. An unprivileged local user can trigger this condition by inducing memory pressure on an affected system. The kernel packages in Red Hat Enterprise Linux 8 and 9 and the Red Hat Enterprise Linux CoreOS (RHCOS) kernels shipped with OpenShift Container Platform 4 are affected; Red Hat Enterprise Linux 7 is not affected because the vulnerable code is not present. The fix is deferred for the affected streams because the CVSS 3.1 score is below 7.0, so no trackers are being filed at this severity; the residual risk is limited to rcu_tasks stall warnings and temporary system unresponsiveness during heavy memory reclaim, with no impact on confidentiality or integrity. Upstream addressed this by using cond_resched_tasks_rcu_qs() in shrink_lruvec(), which reports a quiescent state even when cond_resched() does nothing.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity,Confidentiality,Other
Technical Impact: Modify Application Data; Read Application Data; Alter Execution Logic; Unexpected State
If access to a shared resource is not correctly synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.