CVE-2026-99649

Description

A flaw was found in the Linux kernel's Kernel Samepage Merging (KSM) subsystem. A local attacker can cause a denial of service (DoS) due to missing compatibility checks on large swap-cache memory allocations (folios) prior to mapping them. When shared memory slots are read back as part of a large folio, the kernel bypasses verification, allowing an incompatible memory mapping to be established. Consequently, reverse mapping fails to find the new mapping, preventing memory migration or reclamation and potentially exhausting system memory.

Statement

This vulnerability is rated as Low impact for Red Hat Enterprise Linux because exploitation requires local access under specific memory swapping conditions, and the impact is confined to preventing memory page migration or reclamation. Furthermore, Kernel Samepage Merging (KSM) is disabled by default on standard Red Hat Enterprise Linux installations, limiting exposure to systems where memory deduplication has been explicitly enabled. In vulnerable configurations, unprivileged local users can at most cause degraded memory reclamation rather than arbitrary code execution or data disclosure.

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 Score2.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an attacker can create the conditions that mistakenly release a reference to a resource, then the attacker could prevent the resource from being reclaimed, deplete the available resource pool, and prevent other processes or threads from accessing the same type of resource.

Frequently Asked Questions

Want to get errata notifications? Sign up here.