CVE-2026-89758
Description
A flaw was found in the Linux kernel's memory management subsystem. When an HMM-based Graphics Processing Unit (GPU) driver migrates a Transparent Huge Page (THP) to device memory, it can leave a device-private Page Middle Directory (PMD) entry. If a user-space application then attempts to manage this memory range, the kernel may incorrectly process the non-present PMD, leading to a system crash. This vulnerability could allow a local attacker to cause a Denial of Service (DoS).
Statement
A device-private non-present PMD can reach queue_folios_pmd() and be passed to pmd_folio(), which interprets the software entry as a hardware PFN and produces a bogus folio pointer. The immediate result may be a VM_BUG_ON, an invalid vmemmap dereference, or a kernel oops. If the encoded PFN aliases a valid page, the MM code may instead isolate an unrelated live folio from the LRU and pass it into later page migration processing. For the CVSS the PR:L value is used because an unprivileged local user may operate on memory in its own process, although an HMM capable GPU driver, an anonymous THP migrated to device memory, and a matching mempolicy operation are required. The issue is not network reachable. Impact is at least a local denial of service via kernel crash and in the worst case may affect confidentiality and integrity through wrong folio manipulation. The aliasing case is a memory corruption candidate and should be reviewed for refcount, LRU, and migration side effects before privilege escalation is ruled out.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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 | 7.8 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.