CVE-2026-99648

Description

A flaw was found in the Linux kernel's memory management subsystem. During a partial merge of Virtual Memory Areas (VMAs), the kernel fails to verify driver alignment constraints before shifting memory boundaries. A local user with access to certain memory-mapped character devices can exploit this flaw by modifying memory protections to trigger an invalid merge. This causes the kernel to misinterpret page table structures and process user-controlled memory as page tables, leading to memory corruption, a Denial of Service (DoS), or potentially privilege escalation.

Statement

This vulnerability is rated as Moderate impact because exploitation requires local access, specific device node access permissions, and complex memory orchestration to achieve privilege escalation or cause a system crash. In typical Red Hat Enterprise Linux environments, unprivileged users do not have access to character devices backed by direct access memory drivers with custom alignment requirements. Consequently, the flaw cannot be triggered remotely or under default system configurations without access to specialized persistent-memory devices.

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 Score7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Other

Technical Impact: Varies by Context

When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.

Availability,Integrity,Confidentiality

Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart

If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.