CVE-2024-48876

Description

A flaw was found in the Linux kernel's stack depot subsystem. A local user could cause a Denial of Service (DoS) by triggering conditions that result in a kernel deadlock and system hang. This issue occurs when a non-maskable interrupt (NMI)—a high-priority hardware signal—is handled while an internal memory lock is already in use, causing the kernel to attempt to acquire the lock a second time.

Statement

This vulnerability is classified as Moderate impact because successful exploitation is restricted to local denial of service via a kernel hang and cannot lead to code execution or privilege escalation. Under standard Red Hat Enterprise Linux deployments, triggering this condition requires an uncommon timing race where an interrupt occurs in non-maskable interrupt (NMI) context precisely while the stack depot spinlock is held, typically during kernel tracing or diagnostic events. Consequently, the flaw presents limited practical exposure in production systems.

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 Score75.5N/A
Attack VectorLocalLocalN/A
Attack ComplexityHighLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityHighNoneN/A
Integrity ImpactHighNoneN/A
Availability ImpactHighHighN/A

Vector

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

NVD: 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 (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart

Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.