CVE-2026-99644
Description
A flaw was found in the Linux kernel's memory tier management subsystem. A local user could exploit this flaw to cause a Denial of Service (DoS) by triggering a system hang. This issue occurs when removing memory empties a memory tier, resulting in a deadlock between device unregistration and concurrent sysfs file read operations.
Statement
This vulnerability is rated Moderate rather than Important because triggering the deadlock requires local administrative privileges to offline NUMA memory alongside precise timing with sysfs inspection. Standard enterprise deployments rarely decommission memory tiers on running systems, which minimizes practical exposure. Although a successful exploit results in an unrecoverable system freeze, it cannot be leveraged remotely and does not affect data confidentiality or integrity.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.1 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | High | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:H/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
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.