CVE-2026-93241

Description

A flaw was found in the Linux kernel. When the out-of-memory (OOM) killer terminates a multi-threaded process and asynchronous memory cleanup cannot complete, exiting threads continue to invoke memory reclamation and serialize behind an internal lock. A local user can exploit this vulnerability by triggering memory exhaustion with heavily multi-threaded workloads, causing severe system stalls and a denial of service (DoS).

Statement

This vulnerability has been rated as having Low impact by Red Hat because an attacker must already possess local system access and sustain anomalous, highly multi-threaded processes to trigger prolonged exit stalls rather than causing kernel panics or data corruption. Standard deployments under default configurations enforce resource constraints that hinder an unprivileged account from establishing the required thread density and memory pressure. Furthermore, most stable enterprise platform releases are unaffected because the underlying logic is present only in newer kernel baselines.

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 Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/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:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Other)

When an attacker can control a lock, the program may wait indefinitely until the attacker releases the lock, causing a denial of service to other users of the program. This is especially problematic if there is a blocking operation on the lock.

Frequently Asked Questions

Want to get errata notifications? Sign up here.