CVE-2026-98414

Description

A flaw was found in the Linux kernel. An issue in the memory control group (memcg) subsystem occurs when memory allocated within a child control group is transferred to the root group upon group deletion. Subsequent memory reclamation improperly charges pages to the root group without ever uncharging them. A local user could exploit this flaw to cause kernel warnings and an internal memory accounting leak, potentially leading to a Denial of Service (DoS).

Statement

A low severity flaw was found in the Linux kernel's memory control group (memcg) subsystem. When a direct child of the root control group is removed, its object charges are reparented to the root memcg. Because obj_cgroup_charge_pages() does not short-circuit the root memcg, subsequent memory reclamation of the reparented pages (demonstrated through zswap) charges them to the root memcg and triggers a kernel WARNING in refill_stock(). As the corresponding uncharge path skips the root memcg, the root's page counter grows without ever being uncharged, resulting in an internal memory accounting leak that is not directly user-visible, since memory.current is not exposed for the root cgroup. Exploitation requires local access with administrative (root) privileges, because triggering the issue involves creating and removing a direct child of the root cgroup and triggering proactive memory reclaim on the root cgroup; the practical consequence is kernel warning output and an internal accounting leak rather than memory exhaustion or a system crash, which is reflected in the low Red Hat severity rating. Among Red Hat products, the vulnerable code is present only in the Red Hat Enterprise Linux 10 kernel streams rhel-10.3.z and rhel-10.4 and in the Red Hat In-Vehicle OS 2 kernel streams; other Red Hat Enterprise Linux streams (including rhel-10.0.z and rhel-10.2.z) and the OpenShift Container Platform RHCOS kernels are not affected because the vulnerable code is not present in those versions. For the affected streams the fix is deferred to a future update given the low severity and the limited practical impact of the flaw; the residual risk is that a privileged local user performing this specific cgroup removal and reclaim sequence can generate kernel warnings and an internal, non-user-visible accounting leak on the root memcg.

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 HatNVDcve.org
Base Score2.3N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker that can trigger an assert statement can still lead to a denial of service if the relevant code can be triggered by an attacker, and if the scope of the assert() extends beyond the attacker's own session.

Frequently Asked Questions

Want to get errata notifications? Sign up here.