CVE-2026-93237
Description
A flaw was found in the Linux kernel. An incorrect physical memory boundary check on LoongArch systems allows device memory allocations to fall outside the supported virtual memory mapping space. When the kernel attempts to map this out-of-bounds memory, an address wraparound occurs that silently corrupts kernel page tables. A local user could exploit this flaw during device memory operations to potentially achieve privilege escalation or cause a system crash resulting in a denial of service (DoS).
Statement
An incorrect physical memory search limit on LoongArch can allow get_free_mem_region or mhp_get_pluggable_range to select a ZONE_DEVICE range outside the vmemmap covered physical address space. The resulting address wraparound in vmemmap_populate can map the memmap range into low memory and silently corrupt kernel page tables. The direct observed impact includes crashes and failures during device memory initialization, while page table corruption may also permit confidentiality or integrity impact if an attacker can influence the affected allocation path. For the CVSS the PR:L value is used for the paranoid score because access to accelerator or device memory management may be delegated to a local user or service account in some deployments. Exploitation still requires a vulnerable LoongArch CPU configuration with fewer physical address bits, a compatible ZONE_DEVICE driver, and a triggering device memory operation, so AC:H is appropriate. The issue is not network reachable. Impact is at least a local denial of service and in the worst defensible case may include privilege escalation through page table corruption.
Mitigation
Mitigation for this issue is either not available or the currently available options don't 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 | 4.7 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.