CVE-2026-99659

Description

A flaw was found in the Linux kernel's memory management subsystem. An integer truncation vulnerability in the Translation Lookaside Buffer (TLB) flushing mechanism causes memory flush requests of four gigabytes or larger to be truncated. As a result, when large memory regions are unmapped, the kernel fails to invalidate stale address translations. A local user could exploit this flaw to trigger memory corruption or a Denial of Service (DoS).

Statement

Red Hat rates this vulnerability as Important because an authenticated local attacker could leverage retained address translations to corrupt system memory or elevate privileges, breaching fundamental kernel isolation boundaries. Triggering this condition requires an unprivileged process to unmap contiguous memory blocks exceeding four gigabytes, scenarios typically encountered when using hugetlb or large folio mappings on architectures such as arm64. While systems operating under default configurations without extensive huge page mappings face lower operational exposure, multi-tenant environments remain vulnerable to local compromise.

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 Score7.8N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/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:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Other,Integrity

Technical Impact: Unexpected State; Quality Degradation

The program could wind up using the wrong number and generate incorrect results. If the number is used to allocate resources or make a security decision, then this could introduce a vulnerability.

Frequently Asked Questions

Want to get errata notifications? Sign up here.