CVE-2026-99738

Description

A flaw was found in the Linux kernel's shared memory (shmem) subsystem. When swapping in large memory entries, an allocation failure mishandles internal tracking values, incorrectly converting an out-of-memory error into an entry-already-exists error. Because the kernel continuously retries operations upon receiving this error code, persistent allocation failures cause the affected task to spin indefinitely. A local user can exploit this behavior to cause high CPU consumption and a denial of service (DoS).

Statement

This vulnerability is rated as having Moderate impact because exploitation is constrained to authenticated local users, requires severe memory pressure, and results in a denial of service without compromising system confidentiality or integrity. On standard Red Hat Enterprise Linux deployments, shared memory is an integral component, but triggering the condition demands that the kernel repeatedly fail memory allocations while retrieving swapped-out shared folios. An unprivileged local user could potentially induce high CPU utilization or cause the affected process to hang indefinitely in an unrecoverable state.

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: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Amplification

An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.

Frequently Asked Questions

Want to get errata notifications? Sign up here.