CVE-2026-99697

Description

A flaw was found in the Linux kernel's memory management subsystem. When memory limits are exceeded in a dying memory control group (memcg), background memory reclaim operations can execute without holding a valid reference to the cgroup during teardown. This issue can result in a null pointer dereference or a use-after-free condition, allowing a local user to cause a system crash and Denial of Service (DoS).

Statement

This vulnerability is rated as having Moderate severity because exploitation requires local access to manipulate memory cgroups under high memory pressure, limiting the impact to a denial of service via a kernel crash with no risk to system confidentiality or data integrity. In standard Red Hat Enterprise Linux deployments, cgroup hierarchy creation and memory threshold management are handled by privileged system services and container runtimes. Consequently, an unprivileged local user cannot readily force the simultaneous allocation and teardown sequence required to trigger this race condition unless explicitly granted delegated control over cgroup subtrees.

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 Score4.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart

NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.

Integrity,Confidentiality

Technical Impact: Execute Unauthorized Code or Commands; Read Memory; Modify Memory

In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.