CVE-2026-99663

Description

A flaw was found in the Linux kernel's memory management subsystem. When pinning shared memory pages using the memfd_pin_folios() function, the kernel fails to check whether newly allocated memory in the cache has been initialized and marked up to date. A local attacker can exploit this vulnerability to read uninitialized memory, leading to information disclosure.

Statement

This vulnerability is rated as Moderate severity because it is constrained to local information disclosure without enabling modification of kernel memory or direct privilege elevation. In typical Red Hat Enterprise Linux environments, an attacker must possess local execution access to trigger folio pinning on fallocated shared memory, such as through user-space DMA buffer interfaces. The issue only exposes uninitialized page cache data and does not compromise system integrity or cause a denial of service.

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 Score5.5N/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 ImpactNoneN/AN/A
Availability ImpactNoneN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.