CVE-2026-99656

Description

A flaw was found in the Linux kernel's memory management subsystem. A local user can cause data loss by issuing a MADV_FREE request on a memory page managed by Kernel Samepage Merging (KSM). Because the kernel incorrectly clears the page's modified status while it remains eligible for deduplication and sharing, memory reclamation can discard data that other processes still require. This leads to unexpected data loss or corruption for applications relying on the shared memory.

Statement

This vulnerability is rated as Moderate severity because exploitation requires local access alongside specific timing conditions, and Kernel Samepage Merging (KSM) is disabled by default in standard Red Hat Enterprise Linux configurations. Under memory pressure, an unprivileged local user could leverage MADV_FREE advice on deduplicated pages to cause the kernel to discard active page contents, resulting in silent data corruption or application denial of service. The flaw does not allow direct privilege escalation or disclosure of system memory, limiting the overall security blast radius.

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 Score6.3N/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 ImpactHighN/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:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data; Read Memory

If the released resource is subsequently reused or reallocated, then a read operation on the original resource might access sensitive data that is associated with a different user or entity.

Availability

Technical Impact: Unexpected State; DoS: Crash, Exit, or Restart

When the resource is released, the software might modify some of its structure, or close associated channels (such as a file descriptor). When the software later accesses the resource as if it is valid, the resource might not be in an expected state, leading to resultant errors that may lead to a crash.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands; Modify Application Data; Modify Memory

When the resource is released, the software might modify some of its structure. This might affect logic in the sections of code that still assume the resource is active. If the released resource is related to memory and is used in a function call, or points to unexpected data in a write operation, then code execution may be possible upon subsequent accesses.

Frequently Asked Questions

Want to get errata notifications? Sign up here.