CVE-2026-99650

Description

A flaw was found in the Linux kernel's Kernel Samepage Merging (KSM) memory-deduplication subsystem. When reading memory pages back from swap storage after the original process terminates, the kernel attempts to access an already-freed virtual memory tracking structure. A local user could exploit this flaw during memory swap operations to trigger memory tracking inconsistencies, leading to a system crash and a Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate severity because exploitation requires local system access, relies on complex race conditions during memory swap operations, and results at most in a denial of service without compromising data confidentiality or integrity. On standard Red Hat Enterprise Linux deployments, Kernel Samepage Merging is disabled by default, meaning exposure is limited to environments where deduplication services are intentionally configured and running alongside swap. Standard default installations remain largely insulated from this condition.

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 Score4.7N/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 ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.